Skip to main content
Use this section to troubleshoot issues encountered when calling the API.

​
Common Status Codes

Status CodeNameDescriptionWhat to Do
200SuccessClassification completed successfully.Continue with normal operations.
400Bad RequestInvalid request parameters.Review the error message. See Status 400.
401UnauthorizedMissing or invalid API key.Check that your API key header is present and contains a valid API key.
402Payment RequiredYour account does not have enough credits to complete processing.If you have multiple accounts, make sure you’re using the correct API key. Add more credits to your account.
413Content Too LargeThe document exceeds the 200 MB size limit.Reduce the file size and retry. See Status 413.
415Unsupported Media TypeThe document could not be read or converted.Convert the document to PDF and retry. See Status 415.
422Unprocessable EntityInput validation failed.Review your request parameters. See Status 422.
429Too Many RequestsRate limit exceeded.Wait before retrying. Reduce request frequency and implement exponential backoff.
500Internal Server ErrorServer error during classification.Retry. If the issue persists, contact support@landing.ai. See Status 500.
502Bad GatewayThe classification service returned an error.Retry. If the issue persists, contact support@landing.ai. See Status 502.
504Gateway TimeoutRequest processing exceeded the timeout limit.Reduce document size or number of pages. See Status 504.

​
Status 400: Bad Request

This status code indicates invalid request parameters or client-side errors. Review the specific error message to identify the issue.

​
Error: Invalid document URL

This error occurs when the URL provided in document_url cannot be fetched. The URL may be invalid, unreachable, or return a non-200 response. What to do:
  • Verify the URL is correct and publicly accessible.
  • Confirm the server hosting the document does not require authentication or block external requests.
  • If the document is behind a firewall or requires credentials, download it locally and upload it using the document parameter instead.

​
Status 413: Content Too Large

This error occurs when the document you submit exceeds the 200 MB file size limit. What to do:
  • Reduce the file size before uploading.
  • If the document is a PDF, consider compressing it or splitting it into smaller files before classifying.

​
Status 415: Unsupported Media Type

This error occurs when a document in a supported office format (such as DOCX or PPTX) could not be converted to PDF for processing. This is a server-side conversion failure, not a format restriction. What to do:
  • Convert the document to PDF before uploading and retry.
  • If the error persists, contact support@landing.ai.

​
Status 422: Unprocessable Entity

This status code indicates input validation failures. Review the error message and adjust your request parameters.

​
Error: Unsupported file format

This error occurs when you submit a file type that the API does not support. What to do:
  • Convert your document to a supported format before calling the API.
  • For supported file formats, see Supported File Types.

​
Error: Both document fields provided

This error occurs when you include both document and document_url in the same request. What to do:
  • Include only one document input per request: either upload a file using document or provide a URL using document_url.

​
Status 500: Internal Server Error

This error indicates an unexpected server error occurred during classification. What to do:

​
Status 502: Bad Gateway

This error occurs when the internal classification service fails to process the document, typically due to a transient error in the LLM service. What to do:

​
Status 504: Gateway Timeout

This error occurs when the classification process exceeds the timeout limit. What to do:
  • Reduce the size of your document or the number of pages being classified.
  • If the error persists, contact support@landing.ai.

​
When Are Credits Consumed?

Credits are consumed only when the API returns a 200 status code. All other responses, including errors, do not consume credits.