Quickstart
This guide walks through the most common integration pattern: upload a document, submit it for extraction with Document Insights, and read the structured output.
Prerequisites — you have an API key. See Authentication.
Submit an extract job
Pass the fileId to the extract endpoint. Optionally include a hubId to target a specific Document Insights hub, or let Plextera route automatically.
metadata is optional, but when provided its keys and values must be non-empty strings. hubId is optional; if provided, it must reference an enabled hub in your organization.
The job is created with status: QUEUED. Save the id — you’ll need it in the next step.
Wait for completion
Poll the job until status reaches a terminal state (COMPLETED, FAILED, or REJECTED):
Once outputAvailable: true, the output field is populated.
Instead of polling, set up an event subscription to receive a webhook push when the job completes — no polling loop needed.
Next steps
- Authentication — API key format and usage guidelines
- Events — replace polling with webhook push notifications
- API Reference — full endpoint reference with interactive examples