API Reference (v0.9)
This section provides documentation for the Cryptofuse API v0.9.
Deprecated API Version: The v0.9 API has been deprecated and all endpoints will return error responses. Please upgrade to the v1.0 API for current functionality.
API Basics
Base URL
All API requests should be made to the following base URL:
https://api.cryptofuse.io/v0
Request Format
The Cryptofuse API accepts requests with JSON payloads. Always include the following headers:
Content-Type: application/json
X-API-Key: your_api_key_here
Response Format
All responses are returned in JSON format. However, since the v0.9 API is deprecated, all endpoints will return error responses in this format:
{
"error": "deprecated_endpoint",
"message": "This API endpoint is deprecated in v0.9 and no longer functional. Please use the v1.0 API endpoints instead.",
"request_id": "req_v09_deprecated"
}
Error Codes
When using the v0.9 API, you'll receive the following HTTP status code:
| Status Code | Description |
|---|---|
| 410 | Gone - The endpoint has been deprecated and is no longer available |
Available Resources (Deprecated)
The following endpoints were available in v0.9 but are no longer functional:
Authentication
Payments
Supported Blockchains in v0.9
The v0.9 API supported the following blockchains, but is no longer operational:
| Blockchain | Code | Token | Notes |
|---|---|---|---|
| Ethereum | ETH | USDT | 12 confirmations required |
| Binance Smart Chain | BSC | USDT | 15 confirmations required |
| Bitcoin | BTC | BTC | 2 confirmations required |
| TRON | TRX | USDT | 30 confirmations required |
Limitations in v0.9
The v0.9 API had the following limitations:
- Only supported ETH, BSC, BTC, and TRX blockchains
- Limited to USDT token (except BTC which used native Bitcoin)
- No withdrawal API (managed manually)
- Basic transaction monitoring
- Static exchange rates updated daily
All these limitations have been addressed in the v1.0 API, which is now available.
API Changelog
v0.9 (Deprecated)
- Initial release of the Cryptofuse API
- Basic payment processing functionality
- Support for ETH, BSC, BTC, and TRX blockchains
- API key authentication
v1.0 (Current)
- Support for additional blockchains (including SOL)
- Enhanced payment processing capabilities
- Withdrawal API with cold wallet security
- JWT token authentication
- Real-time exchange rate updates
- Improved transaction monitoring
Upgrading to v1.0
To upgrade to the v1.0 API:
- Update your API endpoint URLs from
/v0/...to/v1/... - Obtain new API credentials through the Cryptofuse dashboard
- Update your authentication method to use JWT tokens
- Test your integration with the v1.0 endpoints
For detailed migration instructions contact our support team at [email protected].