Curfex API is rate limited per minute based on user account basis.

Please refer to API resources rate limit listed below:

| Group | API Request | Rate Limit (requests per minute) | | --- | --- | --- | | Authentication | signin checkToken | 60 | | Event Subscription | subscribeUserJPUpdate subscribeUserHKUpdate subscribeTransferStatus subscribeRegistrationStatus subscribeKycDocFailed generateHMACKey | 10 | | Transfer | payout transferInfoUpdate | 500 | | Wallet | walletHistory walletBalance | 200 | | Enquiry | transferStatus transferRate transferHistory transferBank registrationStatus payoutInfo | 200 |

The rate limit token is recovered in “greedy” way where it regenerates token as soon as possible. For example, for “60 requests per minute”, it will regenerate token in each second.

Each successful API response comes with response header X-Rate-Limit-Remaining value for reference.

Exceeding rate limit

When the rate limit is exceeded, API returns HTTP status code 429 with JSON response body below:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json; charset=UTF-8
{
  "payload": {
    "status": "429 Too Many Requests",
    "message": null,
    "errors": [
      "429 Too Many Requests"
    ]
  }
}

Refer to response header X-Rate-Limit-Retry-After-Seconds to try again after specified period (in second).

Customized rate limit

Please contact us if you need higher limit.