Supported Document Formats

This section lists Document Extraction file formats and related constraints.

Article Overview

This is a format and constraints reference article. For detailed endpoint behavior, see the Document Extraction API article.

Request Parameters (Cross-Link Context)

Name Required Type Description
Authorization Yes header Use Authorization: Token <DISCOVERY_API_KEY> with the extractor endpoint.
file Yes form field Uploaded document for extraction and format handling.
include_metadata No form field Optional boolean to return metadata for extracted files.

Runtime Behavior Summary

Typical runtime behavior for this format reference:

  • 200 for valid extraction requests
  • 401 for invalid or misformatted auth
  • 422 when required multipart fields (for example file) are missing

HTTP Status Codes and Error Handling

HTTP Code When It Happens Typical Response Body What to Do
200 Extraction succeeds Extracted payload Continue processing
401 Invalid token or incorrect auth header format Unauthorized Use token-style auth header
422 Missing required extraction input Validation payload (VALIDATION_ERROR) Provide required fields
429 Shared rate and plan limit condition Too-many-requests response Retry with backoff

Pagination

Not applicable for this catalog article.

Rate Limits and Constraints

Key extraction constraints:

Supported file types confirmed by engineering and QA:

  • .csv
  • .doc
  • .docx
  • .json
  • .pdf
  • .ppt
  • .pptx
  • .tsv
  • .txt
  • .xls
  • .xlsx

Unsupported file types:

  • Any file type not in the supported list above is not supported by the Document Extraction API unless SearchStax publishes updated extractor coverage.
  • Maximum file size: 1 GB
  • Maximum extracted text per request: 100 KiB

Shared platform limits and backoff behavior also apply.

Shared API Foundations

Use these shared references for authentication, request and response structure, and pagination behavior used across Site Search APIs:

Articles in this section