[GET] Get Spot exchange fat finger limit
- Que Nguyen
- allen li
Allow user to get fat-finger limit information on spot exchange depend on CountryCode Query params
Table of Contents
- 1 Table of Contents
- 2 Changelogs
- 3 Fat Finger Limit Resource
- 4 API Definitions
- 4.1 Request
- 4.1.1 Headers
- 4.1.2 Query Parameters
- 4.2 Response
- 4.1 Request
- 5 Rate limit
Changelogs
Version | Date | Changes by | Description of change |
V 1.0.1 | Jul 5, 2024 | Que Nguyen |
|
Fat Finger Limit Resource
CountryCode text 国家代码 Country Alpha Two Code 国家两位代码 |
BuyPriceUpperLimit number 买入价格上限限制 Buy price’s upper limit 买入价格上限限制 |
SellPriceUpperLimit number 卖出价格上限限制 Sell price’s upper limit 卖出价格上限限制 |
BuyNotionalUpperLimit number 买入名义价格上限限制 Buy Notional’s upper limit 买入名义价格上限限制 |
Currency text 货币类型 Currency code 货币类型代码 |
{
"CountryCode": "MY",
"BuyPriceUpperLimit": 100,
"SellPriceUpperLimit": 300,
"BuyNotionalUpperLimit": 10000,
"Currency": "USD"
}
API Definitions
GET /public/v2/exchange/spot/fat-finger-limit
Request
Headers
Authorization text Authorization Bearer access token Ex: |
Query Parameters
CountryCode (required) text 国家代码 Country Alpha Two Code 国家两位代码 |
curl -X 'GET' \
'https://uat-api.redex.eco/public/v2/exchange/spot/fat-finger-limit?CountryCode=VN' \
-H 'accept: application/json'
Response
Response Body |
Data object - Fat Finger Limit resource An object of Fat Finger Limit resource |
Errors list of error objects Please see "Getting Started - #Error Object" for more details 请查看Getting Started - #Error Object以获得更多信息。 |
Meta pagination resource Return Pagination Resource 返回分页信息 |
StatusCode integer Http Status codes standard. Example http状态码，如200，201，404 |
Message text Response message: Success or error message. 返回成功或错误的信息。 |
200 OK
{
"Data": {
"CountryCode": "MY",
"BuyPriceUpperLimit": 100,
"SellPriceUpperLimit": 300,
"BuyNotionalUpperLimit": 10000,
"Currency": "USD"
},
"Meta": null,
"Errors": null,
"StatusCode": 200,
"Message": "Success"
}
400 Bad Request
401 Unauthorized
Rate limit
Rate Limit Algorithm: Fixed Window
In fixed window rate limiting, a fixed time window (e.g., one minute, one hour) is used to track the number of requests or actions allowed within that window. Requests exceeding the limit are either rejected or throttled until the window resets.
Rate Limiting Overview
Our API employs rate limiting to ensure fair usage and protect the performance and availability of the service. Combination of Global Policy and Operation Policy
Global Policy
Rate Limit: 3000 requests per 5 minute(s)
Renewal Period: 300 second(s)
Key: IP Address
Increment Condition: Any Request
Operation Policy
Rate Limit: 60 requests per 1 minute(s)
Renewal Period: 60 second(s)
Key:
accound-idbusiness account Id.Increment Condition: Any Request
Rate Limit Details
Rate Limit by Key:
Key: This ensures that rate limits are applied uniquely for each business account id.
Request Limit: Each key is allowed to make up to 60 requests per minute.
Reset Interval: The limit resets every 60 seconds.
Response Headers:
Retry-After: Sent when the rate limit is exceeded, indicating how long to wait before making another request.
Exceeding the Rate Limit
When the rate limit is exceeded, the API will return a 429 Too Many Requests status code. The response will include a Retry-After header specifying the number of seconds to wait before making a new request.