Icrypex
Icrypex API Information
Icrypex API Link: https://github.com/icrypex-com/apidoc/blob/main/README.md
Base Endpoints
- Base Endpoint:
https://api.icrypex.com
Authentication
Icrypex API Link: https://github.com/icrypex-com/apidoc/blob/main/architecture.md
Every HTTP request must include the following headers:
- ICX-API-KEY: Public API Key
- ICX-SIGN: Signature
- ICX-TS: Timestamp in milliseconds
- ICX-NONCE: Timestamp tolerance in milliseconds
Signature
The signature is a message encrypted with HMAC-SHA256. The HMAC-SHA256 code should be generated using a private key and must include a timestamp (as nonce) and the API key.
Nonce
Nonce is a tolerance for the timestamp value. If your application’s time differs from the server time, the maximum allowed value is 60 seconds (60000 milliseconds). For example, if the nonce value is 15000, the signature will be valid for 15 seconds.
Fields
All responses will be in JSON format.
Timestamp
- Timestamp is an integer value and must represent the current time in milliseconds.
Rate Limits
Icrypex API Link: https://github.com/icrypex-com/apidoc/blob/main/architecture.md
- Action: Specifies the operation performed by the endpoint.
- Method: Indicates the type of HTTP request (
GET,POST,DELETE). - Period: Defines the period for requests.
- Limit: Specifies the maximum allowed requests under the rule.
- Rejected: Indicates the rejection duration when receiving a
429HTTP status code. - Policy: Specifies whether the restriction is applied per IP or per IP and Account during the rejection period.
| Action | URI | Method | Period (sec) | Limit (req) | Rejected (sec) | Policy |
|---|---|---|---|---|---|---|
| Order Insert | /sapi/v1/orders | POST | 60 | 300 | 60 | IP, Account |
| Order Cancel | /sapi/v1/orders/{orderId} | DELETE | 60 | 300 | 60 | IP, Account |
| Open Orders | /sapi/v1/orders/{symbol} | GET | 60 | 300 | 60 | IP, Account |
| Order History | /sapi/v1/orders/history | GET | 60 | 300 | 60 | IP, Account |
| Trades of the Order | /sapi/v1/orders/trades/{orderId} | GET | 60 | 300 | 60 | IP, Account |
| Orderbook | /sapi/v1/orderbook | GET | 60 | 240 | 60 | IP |
| Ticker | /sapi/v1/tickers | GET | 60 | 300 | 60 | IP |
| Account Trades | /sapi/v1/trades | GET | 60 | 180 | 60 | IP, Account |
| Account Spot Wallet | /sapi/v1/wallet/spot | GET | 60 | 120 | 60 | IP, Account |
| Klines | /sapi/v1/trades/kline | GET | 60 | 120 | 60 | IP |
| Kline History | /sapi/v1/trades/kline/history | GET | 60 | 120 | 60 | IP |
| OHLC | /sapi/v1/trades/ohlc | GET | 60 | 120 | 60 | IP |
| Last Trades by Symbol | /sapi/v1/trades/last?symbol={symbol} | GET | 60 | 240 | 60 | IP |
Status Codes
Successful Status Codes
- 200 OK: The request was successfully processed.
- 201 Created: A new resource was successfully created.
- 204 No Content: The resource was successfully deleted.
Client-Side Errors
- 400 Bad Request: The request is invalid or contains missing parameters.
- 401 Unauthorized: Authentication failed.
- 403 Forbidden: You do not have permission to access this endpoint.
- 404 Not Found: The requested data could not be found.
- 422 Unprocessable Entity: The operation could not be completed due to reasons detailed in the response body.
- 429 Too Many Requests: Your requests exceeded the rate limit.
Server-Side Errors
- 500 Internal Server Error: Something went wrong on the server.
- 503 Service Unavailable: Connection lost or the server is unavailable for some reason.
RCXT Icrypex API Information
Icrypex has 1 Base Endpoint:
- apiUrl:
api.icrypex.com
Rate Limits
Each endpoint on Icrypex has a specific rate limit applied according to the action and method.
| Limit (1 dakika) | Spot | Ticker |
|---|---|---|
| Fetch Balances | 120 Request Weight | |
| Fetch Orders | 300 Request Weight | |
| Fetch Trades | 180 Request Weight | |
| Ticker | 300 Request Weight |
Fetch Balances
Spot Balance
- Base Endpoint:
apiUrl(api.icrypex.com) - Endpoint:
/sapi/v1/wallet - RCXT Endpoint:
api/v1/icrypex/balances
The user sends a GET request to query Icrypex wallet balances.
This request must include the required header parameters:
-
ICX-API-KEY and ICX-SIGN values must be included.
-
ICX-TS and ICX-NONCE timestamp values must be provided.
-
Limiter:
- Each API endpoint has a specific Request Weight.
- Spot Balance Request Weight: 120
Response Example:
{
"spot": [
{
"coin": "SHIB", #asset
"total": "41634.28" #total
}
],
"margin": null,
"isolatedMargin": null,
"futures": null,
"earnings": null
}Fetch Trades
Spot Trades
- Base Endpoint:
apiUrl(api.icrypex.com) - Endpoint:
/sapi/v1/trades - RCXT Endpoint:
api/v1/icrypex/trades
The user sends a GET request to query Icrypex spot trades.
This request must include the required header parameters:
-
ICX-API-KEY and ICX-SIGN values must be included.
-
ICX-TS and ICX-NONCE timestamp values must be provided.
-
Query parameters:
startTime: The date to start retrieving data.symbol: The trading pair (e.g. BTCUSDT).fromId: Filter by a specific trade ID.page: Page number, used for pagination.
-
Limiter:
- Spot Trades Request Weight: 180
Response Example:
{
"trades": [
{
"orderId": "226664511", #orderId
"tradeId": "27082209", #orderId
"isBuyer": false, #side
"isMaker": false, #side
"price": "0.07610000", #total
"quantity": "199.90000000", #quantity
"symbol": "ACAUSDT", #pairSymbol
"time": 1737552748284, #date
"commission": "0.01521239", #fee
"commissionCurrency": ""
}
],
"cursor": ""
}Fetch Ticker
Ticker
-
Base Endpoint:
apiUrl(api.icrypex.com) -
Endpoint:
/v1/tickers -
RCXT Endpoint:
api/v1/icrypex/ticker -
Only the
symbolquery parameter is used. (e.g. BTCUSDT)symbol: Specifies the trading pair symbol.
Response Example:
{
"symbol": "BTCUSDT", #symbol
"price": "104562.53000000"
}