API Reference
Errors
HTTP status codes and the error response shape.
Status codes
| Status | Meaning |
|---|---|
| 200 | Success |
| 400 | Bad request (invalid parameters) |
| 401 | Unauthorized (invalid or missing token) |
| 403 | Forbidden (Enterprise required, or insufficient permissions) |
| 404 | Not found (resource missing, or timestamp outside the available window) |
| 422 | Unprocessable entity (validation error) |
| 429 | Too many requests (rate limit exceeded) |
| 500 | Internal server error |
Response shape
{
"error": {
"code": "ERROR_CODE",
"message": "Human-readable description",
"details": {
"valid_range": { "start": "...", "end": "..." }
}
},
"meta": {
"request_id": "...",
"timestamp": "..."
}
}Unexpected failures
If something breaks on Vega's side the response is still the envelope above, with code INTERNAL_ERROR and status 500. The meta.request_id in that response is also sent as the X-Request-Id header; quote it when contacting support and we can find the exact request.