The Enkryptify API uses standard HTTP status codes to indicate success or failure.Documentation Index
Fetch the complete documentation index at: https://docs.enkryptify.com/llms.txt
Use this file to discover all available pages before exploring further.
Response shape
All error responses follow the same shape:message field is always a string. Use the HTTP status code for programmatic branching; use message to surface details to your users or logs.
Status codes
| Status | Meaning | When you see it |
|---|---|---|
200 | OK | Request succeeded |
201 | Created | Resource created successfully |
400 | Bad Request | Request body or query parameters failed validation |
401 | Unauthorized | No token, expired token or invalid token |
403 | Forbidden | Token is valid but lacks permission for this resource |
404 | Not Found | The resource does not exist or you do not have access |
409 | Conflict | A uniqueness or state constraint was violated |
429 | Too Many Requests | You hit the rate limit. See Rate limits |
500 | Internal Server Error | Something went wrong on our side. Please retry, then contact support if it persists |
Example error responses
Validation error (400):
401):
403):
404):
Retrying
5xx errors and 429 are safe to retry with exponential backoff. 4xx errors other than 429 indicate a problem with your request. Retrying without changes will return the same error.