Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.quickei.io/llms.txt

Use this file to discover all available pages before exploring further.

Every Quickei API response includes a standard HTTP status code and a JSON body with a type field (success or error).

​
Success Responses

CodeStatusDescription
200OKRequest completed successfully
{
  "message": {
    "code": 200,
    "success": ["SUCCESS"]
  },
  "data": { ... },
  "type": "success"
}

​
Error Responses

CodeStatusWhen it happens
400Bad RequestInvalid parameters, missing required fields
403ForbiddenInvalid or expired token, insufficient permissions
404Not FoundResource doesn’t exist (e.g. invalid order ID)
422Unprocessable EntityValidation error or invalid state transition
429Too Many RequestsRate limit exceeded — retry after backoff
500Internal Server ErrorUnexpected server error — contact support
{
  "message": {
    "code": 400,
    "error": ["Description of the error"]
  },
  "data": [],
  "type": "error"
}
Always check the type field in the response body rather than relying solely on the HTTP status code. This ensures consistent error handling across your integration.