Every error response from the Shuriken API follows a consistent envelope so you can handle failures predictably across all endpoints.Documentation Index
Fetch the complete documentation index at: https://docs.shuriken.trade/llms.txt
Use this file to discover all available pages before exploring further.
Error format
| Field | Description |
|---|---|
error.code | Machine-readable error code |
error.message | Human-readable explanation |
error.details | Optional additional context (may be null) |
requestId | Unique request identifier for debugging |
Common error codes
| HTTP Status | Code | Typical cause |
|---|---|---|
| 400 | INVALID_PARAMS | Missing or invalid parameters |
| 400 | NO_ROUTE | No swap route found for the given token pair |
| 401 | UNAUTHORIZED | Missing, invalid, or expired API key |
| 403 | FORBIDDEN | Key lacks the required permission scope |
| 404 | NOT_FOUND | Resource does not exist (token, order, etc.) |
| 429 | RATE_LIMITED | Too many requests - slow down |
| 500 | INTERNAL_ERROR | Something went wrong on our end |
Rate limiting
When you exceed your rate limit, the API returns a429 response. Check your current usage and limits at any time:
Handling errors
Build resilient integrations by checking the HTTP status code anderror.code field:
Python