Getting Started
Errors
Diagnose and resolve API errors with ease.
In case of errors during API requests, appropriate HTTP status codes will be returned to indicate the nature of the issue. These status codes help in understanding and resolving errors efficiently. Additionally, error messages may be provided in the response body to offer further insight into the encountered problem.
Refer to the specific HTTP status codes and accompanying error messages to troubleshoot and resolve any encountered errors:
Status code | Description | |
---|---|---|
200 | OK | Everything worked as expected. |
400 | Bad Request | The request was unacceptable, often due to missing a required parameter. |
401 | Unauthorized | No valid API key provided in the x-api-key header. |
402 | Request Failed | The parameters were valid but the request failed. |
403 | Forbidden | The API key doesn’t have permissions to perform the request. |
404 | Not Found | The requested resource doesn’t exist. |
409 | Conflict | The request conflicts with another request (perhaps due to using the same idempotent key). |
429 | Too Many Requests | Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. |
500, 502, 503, 504 | Server Errors | Something went wrong on The Swarm end. (These are rare.) |