Skip to main content
For the Unstructured Python SDK,
the Unstructured Partition Endpoint returns errors primarily through
the
The following example shows how to handle the preceding errors. In this example,
a required Unstructured API key is intentionally commented out of the code, so that a
The results of running the preceding code are similar to the following:
Partition Endpoint
Endpoint errors
The following information applies to the legacy Unstructured Partition Endpoint.Unstructured recommends that you use the
on-demand jobs functionality in the
Unstructured API instead. Unstructured’s on-demand 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.
UnstructuredClientError class (the base class for all errors raised by the Unstructured Python SDK) and
the HTTPValidationError class (inherited from UnstructuredClientError). Less common errors are returned through the following classes:
httpx.RequestError, the base class for request errors.httpx.ConnectError, for HTTP connection request errors.httpx.TimeoutException, for HTTP request timeout errors.ServerError(inherited fromUnstructuredClientError), for server-side errors.ResponseValidationError(inherited fromUnstructuredClientError), for type mismatches between the response data and the expected Pydantic model.
401 Unauthorized error is intentionally thrown.


