Skip to main content
The following information applies to the legacy Unstructured Partition Endpoint.Unstructured recommends that you use the local-file processing jobs functionality in the Unstructured Pipeline API instead. Unstructured’s local-file processing jobs provide many benefits over the legacy Unstructured Partition Endpoint, including support for:
  • Production-level usage.
  • Multiple local input files in batches.
  • The latest and highest-performing models.
  • Post-transform enrichments.
  • All of Unstructured’s chunking strategies.
  • The generation of vector embeddings.
The Unstructured API also provides support for processing files and data in remote locations.
The Unstructured Partition Endpoint provides parameters to customize the processing of documents. These parameters include: The only required parameter is files - the file you wish to process. The following parameters only apply when a chunking strategy is specified. Otherwise, they are ignored. Learn more. The following parameters are specific to the Python and JavaScript/TypeScript clients and are not sent to the server. Learn more. Need help getting started? Check out the Examples page for some inspiration. Allowed values for vlm_model_provider and vlm_model pairs include the following:
The following models are no longer available as of the following dates:
  • For anthropic, claude-3-5-sonnet-20241022: October 22, 2025
  • For bedrock, us.anthropic.claude-3-5-sonnet-20241022-v2:0: October 22, 2025
Unstructured recommends the following actions:
  • For new workflows, do not use any of these models.
  • For any workflow that uses any of these models, update that workflow as soon as possible to use a different model.
Workflows that attempt to use any of these models on or after its associated date will return errors.