Error Handling

The MultiSave API uses conventional HTTP response codes to indicate the success or failure of an API request.

Error Response Format

All error responses follow a consistent JSON format.

json

{
  "statusCode": 400,
  "message": "Validation failed",
  "error": "Bad Request",
  "details": [
    {
      "field": "email",
      "message": "Invalid email format"
    }
  ]
}

Field	Type	Description
`statusCode`	number	HTTP status code
`message`	string	Human-readable error message
`error`	string	Error type name
`details`	array	Additional error details (optional)

HTTP Status Codes

400Bad Request

The request was malformed or missing required parameters.

Solution: Check your request body and query parameters.

401Unauthorized

Authentication credentials are missing or invalid.

Solution: Verify your API key or JWT token.

403Forbidden

You do not have permission to access this resource.

Solution: Check your subscription plan and permissions.

404Not Found

The requested resource does not exist.

Solution: Verify the endpoint URL and resource ID.

409Conflict

The request conflicts with the current state of the resource.

Solution: Resolve the conflict and retry the request.

422Unprocessable Entity

The request body contains validation errors.

Solution: Check the error details and fix the validation issues.

429Too Many Requests

You have exceeded the rate limit.

Solution: Wait for the rate limit to reset and implement backoff.

500Internal Server Error

An unexpected error occurred on the server.

Solution: Retry the request or contact support if the issue persists.

503Service Unavailable

The service is temporarily unavailable.

Solution: Wait and retry the request with exponential backoff.