Error Handling
Common error messages and their handling.
Last updated
Was this helpful?
⌘Ctrlk
Common error messages and their handling.
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. Provide this code when asking for support.
400
A required request parameter is missing.
401
Invalid API key. Make sure the key starts with md_ and is active.
Make sure you are calling the V2 API, your code should match the samples.
API keys are not JWTs: do not include Bearer in your Authentication header.
Always prefer using the provided SDKs if possible.
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 (usually a processing result).
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. For more information, consult the section: Rate Limits.
500
Failed to run the inference.
Failed to process the request.
Check to make sure that the API is fully operational.
You can also subscribe to be notified automatically.
Last updated
Was this helpful?
Was this helpful?