The Vendaze API uses standard HTTP status codes and returns a consistent error format on every failure.Documentation Index
Fetch the complete documentation index at: https://developers.vendaze.com/llms.txt
Use this file to discover all available pages before exploring further.
Error format
| Field | Description |
|---|---|
code | Machine-readable error code. Use in error handling logic. |
message | Human-readable description for developers. Do not show to end users. |
request_id | Unique request ID. Include when contacting support. |
A 2xx response never contains
error. A non-2xx response always contains error.HTTP status codes
| Status | Meaning |
|---|---|
200 | Success. Resource read or updated. |
201 | Created successfully. |
204 | No content. Resource deleted. Empty body. |
400 | Malformed request or missing required parameter. |
401 | Unauthenticated. Token missing, invalid, or expired. |
403 | Forbidden. Valid token but insufficient scope. |
404 | Not found. Resource does not exist, was deleted, or belongs to another workspace. |
422 | Validation failed. See the fields object. |
429 | Rate limit exceeded. |
500 | Internal error. Something went wrong on the server. |
Error code reference
| Code | HTTP | When it occurs |
|---|---|---|
unauthorized | 401 | Bearer token missing or signature invalid. |
token_expired | 401 | Access token expired. Refresh using the refresh token. |
insufficient_scope | 403 | Token lacks the required scope for this endpoint. |
forbidden | 403 | Authenticated but not allowed to access this resource. |
not_found | 404 | Resource does not exist, was deleted, or belongs to another workspace. |
validation_error | 422 | Input failed validation. See fields for details. |
rate_limit_exceeded | 429 | Too many requests. Wait the time indicated by Retry-After. |
internal_error | 500 | Unexpected error. Use request_id when contacting support. |
Validation errors
When validation fails, the response includes afields object mapping each field to its problem: