Base URL
All requests go to your deployment’s base URL. There is no default.Authentication
Every request carries a JWT access token issued when you sign in to your deployment:401. Pass username and password, or set the environment variables UNSTRUCTURED_USERNAME, UNSTRUCTURED_PASSWORD and UNSTRUCTURED_CLIENT_BASE_URL. Sign-in failures raise an authentication error whose message names the step that failed.
The SDK’s sign-in needs password login. Deployments that sign in through SSO (Entra, Okta) and accounts with MFA are not supported yet.
Background Jobs
Long-running operations (ingestion, batch classification, large exports) return immediately and run in the background. Pass ajob_id of your choosing, then poll Task Tracking:
- Submit the job with a
job_id(a UUID you generate). - Poll
POST /progress_tracker/task_statuswith that id. statusmoves throughin_progresstocompleted,failed, oraborted, withpercent_completealong the way.
Pagination
List endpoints that can return large results offer a paginated variant (/metadata/list_paginated) using limit and offset, returning next_offset until it is null.
Errors
Standard HTTP status codes:400 bad request, 401 authentication, 403 permission, 404 not found, 409 conflict, 422 validation, 429 rate limit, 5xx server. The SDK retries twice by default on retryable failures and raises typed exceptions per status.