Usage Details
Authentication
All endpoints require authentication using a pair of keys provided by Biso: client_id and api_key. Both must be included as headers in every request, as shown below:
x-biso-client-id: <client_id>
x-biso-api-key: <api_key>
How can I get my authentication keys?
Please enter in contact with Biso
Rate Limit Details
All API endpoints are limited to 1000 requests per minute per IP. This limit applies to all operations, not just order-related endpoints.
What happens if you exceed the limit?
If the rate limit is exceeded, the API returns a 429 Too Many Requests error. The response includes a Retry-After header with the number of seconds to wait before retrying.
Example 429 Response:
HTTP/1.1 429 Too Many Requests
Connection: keep-alive
Content-Length: 0
Date: Fri, 27 Jun 2025 12:51:31 GMT
Retry-After: 60
Server: awselb/2.0
Best Practices for Clients
- Always respect the Retry-After value before sending new requests.
- Consider implementing exponential backoff when handling 429 errors.
- For large volumes, consider batching requests and monitoring your throughput.
Error Handling
429 Too Many Requests: You have exceeded the allowed rate limit. Wait the number of seconds specified in the Retry-After header before retrying.
404 Not found: The requested resource could not be found. This may occur if the endpoint is incorrect, the resource ID does not exist, or the resource has been deleted.
Best Practices
- When you have updates in your order total value, It's recommended to update the payments values to match the new order total value.
Uncommon Cases
How to add new items to an order?
There's no way to add new items to existing orders. To do so, you'll need to cancel the current order and create a new one.
Contact and Support
For further information, troubleshooting, or to request access, please contact Biso support via Help Biso