Error Documents

An error document is returned when the API encounters an error. Note that error documents are not always returned. See the example error document below for more information regarding the document structure.

Example

{
  "error": {
    "message": "The service received an invalid zipCode: 94107f",
    "code": "600-0043",
    "requestId": "91da80e4eb4b1a8d7da08ae04d2b4cf4"
  }
}

Error Code References

The application-level error code is comprised of a 3 digit application prefix and a 4 digit application error code.

Gateway error codes are prefaced with '000-'.

Error CodeDescriptionHTTP Status
600-0000Unhandled Error (System/OS Error)400
600-0010Internal Server Error400
600-0020Authorization Error403
600-0025Username, Tenant, and Role Not Authorized403
600-0030Document Not Found404
600-0031Invalid Document Id400
600-0032Invalid Document Class400
600-0033Unknown path (check documentation)400
600-0040Missing Parameter400
600-0041Invalid Data Type400
600-0042Invalid Content Type400
600-0043Invalid Request Value400
600-0044AbiliTec Link Error400
600-0045Invalid Request Parameter400
600-0050Conflicting Values for Parameter and Header400
600-0060Batch Request Limit Exceeded400
600-0070Generic Backend Service Error400
600-0080Generic Backend Service Error400
600-0095Generic Backend Service Error400
600-0100Generic Backend Service Error400

📘

Cloudflare Error Codes

All client requests are routed through Cloudflare for additional security. This means you might receive an error code from Cloudflare itself in some scenarios, such as when calls are made from an IP address that is not whitelisted. These error codes are described here: https://support.cloudflare.com/hc/en-us/sections/200820298-Cloudflare-Errors.