Status
Current availability of platform services, and a reference for the status codes you may see in API responses.
Services
| Service | Description | Status |
|---|---|---|
| API | Public REST endpoints under /api/v1 |
Operational |
| Webhooks | Outbound event delivery to your endpoints | Operational |
| Dashboard | Web console for managing projects and keys | Operational |
| Documentation | This site and downloadable SDK references | Operational |
Status codes
The API uses standard HTTP status codes. The most common ones are listed below.
| Code | Meaning | What to do |
|---|---|---|
200 OK | The request succeeded. | Nothing. |
201 Created | A new resource was created. | Read the Location header. |
400 Bad Request | The body or parameters are malformed. | Check the error.details field. |
401 Unauthorized | The API key is missing or invalid. | Send a valid Authorization: Bearer header. |
403 Forbidden | The key lacks permission for this action. | Request a broader scope. |
404 Not Found | The resource or route does not exist. | Verify the ID and path. |
429 Too Many Requests | You have exceeded the rate limit. | Wait for the time in Retry-After, then retry. |
500 Internal Server Error | Something failed on our side. | Retry with backoff. Report it if it persists. |
503 Service Unavailable | The service is temporarily down for maintenance or load. | Retry later. Check the table above. |
Subscribe to updates
Incidents and scheduled maintenance are posted to the status feed at /docs/status.json. Maintenance windows are announced at least 72 hours in advance.