API Error Codes Reference
API Now! uses the RFC 9457 (“Problem Details for HTTP APIs”) standard for all API error responses. This format provides machine-readable error details while remaining human-readable, helping both API consumers and API authors troubleshoot issues quickly.
Standard Error Response Format
Section titled “Standard Error Response Format”All error responses from the Serverless Engine return the application/problem+json content type and contain the following standard fields:
| Field | Type | Description |
|---|---|---|
type | string | A URI reference that identifies the specific error type and points to its documentation (like this guide). |
title | string | A short, human-readable summary of the error type. |
status | integer | The HTTP status code returned by the server (e.g., 400, 403, 422). |
code | string | A unique, uppercase machine-readable error identifier (e.g., VALIDATION_ERROR). |
detail | string | A detailed, context-specific explanation of why this error occurred. |
instance | string | A URI reference for the specific endpoint where the error occurred. |
errors | array | (Optional) A list of specific field-level validation errors (used primarily in validation errors). |
List of Standard Errors
Section titled “List of Standard Errors”Below is the directory of all standard errors returned by the API Now! runtime:
400 Bad Request Errors
Section titled “400 Bad Request Errors”- Invalid Request Format (
INVALID_REQUEST_FORMAT): Mismatched braces or malformed JSON payloads. - Invalid Query Parameter (
INVALID_QUERY_PARAM): Invalid sorting, filtering, or paging parameters in the query string. - Bad Request (
INVALID_REQUEST): Malformed requests or actions that are not supported.
401 & 403 Access Control Errors
Section titled “401 & 403 Access Control Errors”- Unauthorized (
AUTHENTICATION_FAILED): Missing, expired, or malformed authentication credentials. - Authorization Denied (
AUTHORIZATION_DENIED): Role-based access control (RBAC) violations.
404 & 405 Route Errors
Section titled “404 & 405 Route Errors”- Resource Not Found (
RESOURCE_NOT_FOUND): The requested endpoint or record does not exist. - Method Not Allowed (
METHOD_NOT_ALLOWED): The HTTP method is not supported on this endpoint.
409 & 422 Data Integrity Errors
Section titled “409 & 422 Data Integrity Errors”- Conflict (
RESOURCE_CONFLICT): Duplicate entries for unique properties (like email or username). - Validation Error (
VALIDATION_ERROR): Data values that fail field constraints or system rules.
500 Internal Server Errors
Section titled “500 Internal Server Errors”- Too Many Requests (
RATE_LIMIT_EXCEEDED): The client has sent too many requests in a given amount of time. - Internal Server Error (
INTERNAL_SERVER_ERROR): An unexpected crash or database error occurred.