Vault
HTTP Status Codes
Status codes returned by Ozura Vault API.
Reference for HTTP status codes returned by Vault endpoints.
For specific messages and troubleshooting, see Common errors. For integration patterns, see Error handling.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Status codes returned by Ozura Vault API.
| Code | Status | Description |
|---|---|---|
| 200 | OK | Request succeeded |
| 201 | Created | Resource created (e.g. token) |
| Code | Status | Common causes |
|---|---|---|
| 400 | Bad Request | Invalid JSON, missing/invalid fields, invalid card number |
| 401 | Unauthorized | Missing or invalid API key, expired JWT |
| 403 | Forbidden | MFA required, insufficient permissions, account locked |
| 404 | Not Found | Token or resource doesn’t exist or was deleted |
| 409 | Conflict | Duplicate resource (e.g. application name) |
| 429 | Too Many Requests | Rate limit exceeded; use retry_after_seconds if present |
| Code | Status | Action |
|---|---|---|
| 500 | Internal Server Error | Retry with backoff |
| 502 | Bad Gateway | Proxy/upstream error; retry |
| 503 | Service Unavailable | Retry after delay |
| 504 | Gateway Timeout | Upstream timeout; retry |
{
"success": false,
"message": "Human-readable error message",
"data": null
}