Response Codes - Quickei Developer Docs

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

Success Responses

Code	Status	Description
`200`	OK	Request completed successfully

{
  "message": {
    "code": 200,
    "success": ["SUCCESS"]
  },
  "data": { ... },
  "type": "success"
}

Error Responses

Code	Status	When it happens
`400`	Bad Request	Invalid parameters, missing required fields
`403`	Forbidden	Invalid or expired token, insufficient permissions
`404`	Not Found	Resource doesn’t exist (e.g. invalid order ID)
`422`	Unprocessable Entity	Validation error or invalid state transition
`429`	Too Many Requests	Rate limit exceeded — retry after backoff
`500`	Internal Server Error	Unexpected 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.