Error Handling

Common error messages and their handling.

Error Responses

All errors will contain the following information:

  • Status: the HTTP status code.

  • Title: a human-readable short description, it may not be unique.

  • Detail: a human-readable description of the error, it will be unique.

  • Code: a code to identify the specific error.

4xx Errors - Client Errors

HTTP Status
Possible Reasons

400

  • A required request parameter is missing.

401

  • Invalid API key. Make sure the key starts with md_ and is active.

402

  • An optional feature is not in your plan.

  • Your subscription is either not active or exceeded limits.

403

  • You don't have access to the requested resource.

404

  • The requested resource does not exist.

  • The requested resource is not ready for use.

422

  • Wrong format for a UUID.

  • Invalid or empty file sent.

  • Invalid parameter sent in a request.

429

  • Too many requests. Wait a few seconds and try again.

5xx Errors - Server Errors

HTTP Status
Possible Reasons

500

  • Failed to run the inference.

  • Failed to process the request.

Last updated

Was this helpful?