Reference
Errors
Error response shape and common HTTP status codes.
Modified at Apr 28, 2026, 05:38 AM UTC
REST errors are JSON and include a trace ID.
{ "error": true, "code": "REQUEST_NOT_MATCH_SPEC_ERROR", "message": "Ada yang salah dengan input kamu, cek kembali yuk!", "source": "body", "errors": { "amount": ["Invalid input: expected number"] }, "traceId": "01234567-89ab-cdef-0123-456789abcdef"}Common Status Codes
| HTTP status | Meaning |
|---|---|
| 400 | Malformed body, unsupported content type, or bad request syntax. |
| 401 | Missing or invalid API key. |
| 402 | Insufficient balance for a paid action. |
| 403 | The API key cannot access the requested feature. |
| 404 | The resource does not exist or is not owned by the authenticated user. |
| 409 | Conflict, including idempotency conflicts. |
| 422 | Request validation failed or order data does not match the service schema. |
| 429 | Rate limit exceeded. |
| 500 | Internal server error. |
| 503 | Service or provider is unavailable. |
Validation Sources
| Source | Meaning |
|---|---|
| body | JSON body failed validation. |
| query | Query string failed validation. |
| headers | Header failed validation. |
| params | Path parameter failed validation. |
| order | POST /api/order payload failed the service schema. |