Skip to main content
For some API requests, the response body is created by the gateway itself — usually in error situations, or when the gateway must replace the upstream server’s response. You can detect these responses by a dedicated header — when it is present, the response body was generated by the gateway:
The gateway-generated error responses are listed below.

Error Messages

Every error response carries a message field. An example response:
Billing-related errors (status 402) also carry machine-readable fields so your code does not have to parse the message: reason (not_included, quota_exceeded or insufficient_balance) and — when a specific billable object caused the rejection — object with that object’s slug. An example response:
Below is a list of error messages: