Error Response

When working with the Mirako API, you may encounter various errors due to incorrect requests, server issues, or other unexpected conditions. Here are the errros you might encounter.

HTTP Status Codes

The Mirako API uses standard HTTP status codes to indicate the success or failure of requests:

Success Codes

200 OK: Request succeeded
204 No Content: Request succeeded (for delete operations)

Client Error Codes

400 Bad Request: Invalid request format or parameters
401 Unauthorized: Invalid or missing API key
402 Payment Required: Insufficient funds or payment required
403 Forbidden: Insufficient permissions or quota exceeded
404 Not Found: Resource doesn't exist
422 Unprocessable Entity: Valid request format but invalid data
429 Too Many Requests: Rate limit exceeded

Server Error Codes

500 Internal Server Error: Unexpected server error
503 Service Unavailable: Service temporarily unavailable

Error Response Format

Error responses follow this standard format. Note not all errros will include response body.

json

{
  "title": "Bad Request",
  "status": 400,
  "detail": "The 'image' field is required but was not provided.",
  "errors": [
    {
      "location": "body.image",
      "message": "Required field is missing",
      "value": null
    }
  ]
}