Skip to main content
deAPI uses conventional HTTP response codes to indicate the success or failure of an API request. Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error from the provided information (e.g., missing required parameter, unauthorized access). Codes in the 5xx range indicate an error with deAPI servers.

HTTP Status Codes

Error Response Format

All error responses follow a consistent JSON structure:
object | null
Always null for error responses.
string
Human-readable error description.
array
Additional error details. For validation errors (422), contains field-specific messages.
integer
HTTP status code (matches the response status).

Error Types

401 Unauthorized

Returned when authentication fails. Common causes:
  • Missing Authorization header
  • Invalid API key
  • Expired API key
Solution: Verify your API key is correct and included in the Authorization: Bearer <API_KEY> header.

404 Not Found

Returned when the requested resource doesn’t exist. Common causes:
  • Invalid request_id when polling results
  • Model name doesn’t exist
  • Request ID not found
Solution: Verify the resource identifier (request_id, model name) is correct. Use the Model Selection endpoint to get valid model names.

422 Unprocessable Entity

Returned when request validation fails. The errors array contains field-specific details. Common causes:
  • Missing required parameters
  • Invalid parameter values (out of range, wrong type)
  • Invalid image/video URL or format
Solution: Check the errors array to identify which fields failed validation and correct them according to the API documentation.

500 Internal Server Error

Returned when an unexpected error occurs on our servers.
Solution: Wait a moment and retry your request. If the problem persists, check status.deapi.ai or contact support on Discord.

Best Practices

Handle all error codes

Implement error handling for all possible status codes in your application.

Parse the errors array

For 422 responses, iterate through the errors array to display field-specific messages to users.

Implement retry logic

For 500 errors, implement exponential backoff retry (e.g., 1s, 2s, 4s delays).

Log error responses

Log full error responses for debugging. Include request_id if available.

Example Error Handling