Skip to main content
Complete the requirements before you begin. You can learn about Unstructured’s partitioning and structured data extraction before you begin.
1

Create the job

Replace EXTRACTION_PROMPT with your extraction prompt, and INPUT_DIR with the path to your local directory of files to process. The response includes the job ID.
Each local-file processing job can include up to 10 files, and each file can be up to 50 MB.These local-file processing jobs are on-demand jobs. A job enters the queue if the Workspace is running its allowed number of on-demand jobs or an earlier job is queued. By default, send at most one queued submission per second per Workspace. Another queued submission within that second returns HTTP 429. Jobs that start without entering the queue do not count toward this limit.For Unstructured SaaS accounts, up to five on-demand jobs can run at once per Workspace. Accepted queued jobs remain scheduled until capacity is available. Your deployment settings can change both this capacity and the queued-submission rate.For other Pipelines API limits, see Pipelines API rate limits.
Save and run this script:
This script requires jq to parse the JSON response.
2

Poll for job status

Replace JOB_ID with the job ID from the previous step. This script polls every 10 seconds and stops when the job completes.
Save and run this script:
This script requires jq to parse the JSON response.
3

Download the job output

Replace JOB_ID, OUTPUT_FILE_IDS, and OUTPUT_DIR with your values from the previous steps.
Save and run this script:

Complete end-to-end script

Replace EXTRACTION_PROMPT, INPUT_DIR, and OUTPUT_DIR with your values, then save and run this script.
This script requires jq to parse JSON responses.

What’s next?