Troubleshoot Extraction

​

Common Status Codes

​

Status Codes

​

Status 400: Bad Request

​

Error: Failed to download document from URL

Failed to download document from URL: {error_details}

• Verify the URL is accessible and returns valid content.
• Check network connectivity and URL permissions.
• Ensure the URL points to a Markdown file (.md extension).

​

Error: Field extraction invalid

Field extraction invalid: {error_details}

• Review the error details in the response.
• Verify the JSON schema follows the guidelines described in Extraction Schema (JSON). Update your JSON schema if needed.
• Ensure all required fields are properly defined in the schema.
• Check if the document contains data that matches the schema structure.

​

Error: Invalid extract version

Invalid extract version '{version}' provided. Valid versions are: {list_of_versions} or use 'extract-latest' to use the latest version.

• Use one of the supported versions listed in the error message.
• Use extract-latest to automatically use the latest version.
• If you don’t specify a version, the API uses the latest version by default.
• For more information, go to Model Version.

​

Status 422: Unprocessable Entity

​

Error: The provided schema is not valid JSON

The provided string is not valid JSON, let alone a schema.

• Verify your extraction schema is valid JSON.
• Check for syntax errors such as missing commas, quotes, or brackets.
• See Extraction Schema (JSON) for the required structure.

​

Error: The provided schema must have “type”: “object” for the root

Field extraction validation error: The provided schema must have "type": "object" for the root.

{
  "type": "object",
  "properties": {
    "invoice_number": {
      "type": "string",
      "description": "Invoice number"
    }
  }
}

{
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "invoice_number": {
        "type": "string",
        "description": "Invoice number"
      }
    }
  }
}

​

Error: The provided JSON must parse to an object at the root

Field extraction validation error: The provided JSON must parse to an object at the root.

{
  "type": "object",
  "properties": {
    "invoice_number": {"type": "string"},
    "vendor_name": {"type": "string"},
    "total": {"type": "number"}
  }
}

["invoice_number", "vendor_name", "total"]

​

Error: The provided JSON object was not a valid JSON schema

Field extraction validation error: The provided JSON object was not a valid JSON schema. Error: {error_details}

• Review the error details to identify the specific schema issue.
• Check that every type value is a JSON Schema type (string, number, integer, boolean, object, array, or null). A custom type such as "money" fails validation, and the error details report that the value is not valid under any of the given schemas.
• Verify your schema follows the guidelines described in Extraction Schema (JSON).

​

Error: The provided schema contains recursive local $ref cycles

Field extraction validation error: The provided schema contains recursive local `$ref` cycles, which are not supported.

​

Error: Fields the model cannot extract (strict mode)

• Confirm the document actually contains the data for the fields that could not be extracted.
• Refine each field’s description and x-alternativeNames to help the model locate the data. See Field Descriptions and Alternative Names.
• To skip fields that cannot be extracted instead of returning an error, set strict to false.

​

Error: Schema fields not supported (strict mode)

The following schema fields were not supported: {keywords}

• Remove the listed keywords from your schema. See Extraction Schema (JSON) for the supported schema features.
• To ignore unsupported keywords instead of returning an error, set strict to false.

​

Error: Cannot provide both ‘markdown’ and ‘markdown_url’

Cannot provide both 'markdown' and 'markdown_url'. Please provide only one.

• Provide a Markdown file using the markdown parameter, OR
• Provide a URL to a Markdown file using the markdown_url parameter.

​

Error: Provide exactly one Markdown source

provide exactly one of markdown or markdown_url

• Use the markdown parameter to upload a Markdown file, OR
• Use the markdown_url parameter to provide a URL to a Markdown file.

​

Error: No markdown file or URL provided

No markdown file or URL provided.

• If using markdown: Ensure you are uploading a valid Markdown file (not an empty file or blank value).
• If using markdown_url: Ensure the parameter contains a valid URL (not an empty string or blank value).
• Verify that your request properly includes the file or URL value.

​

Error: Invalid URL format

Invalid URL format: {url}

• Verify the URL is properly formatted with a valid protocol (http:// or https://).
• Check for typos or missing characters in the URL.
• Ensure the URL is properly encoded if it contains special characters.

​

Error: Multiple Markdown files detected

Multiple markdown files detected (X). Please provide only one document file.

​

Error: Unsupported format

Unsupported format: {mime_type} ({filename}). Supported formats: MD

• The extract endpoint only accepts Markdown files with a .md extension.
• If you have a PDF, DOCX, or other document format, use the Parse API to convert your document to Markdown first.
• Ensure your file has a .md extension and contains valid UTF-8 encoded Markdown content.

​

Status 500: Internal Server Error

• Retry the request.
• If the error persists, contact support@landing.ai.

​

Status 504: Gateway Timeout

• Reduce the size of your Markdown document.
• Simplify your extraction schema and verify it follows the guidelines described in Extraction Schema (JSON). Update your JSON schema if needed.
• If the error persists, contact support@landing.ai.

​

Extract Jobs

​

Create a Job

​

Get a Job

​

When Are Credits Consumed?