Overview
The Plextera Public API lets you integrate document processing and workflow automation into your applications.
What you can do
Upload PDFs, images, Office files, and more — up to 50 MB per file.
Extract structured fields from documents using hub-configured models.
Start and monitor workflow runs for document processing pipelines.
Receive webhook push notifications when jobs and runs reach terminal states.
How it works
- Upload a document via the Files API to get a
fileId. - Process it — submit a Document Insights extract job, or trigger a workflow that handles the full pipeline.
- React — poll for results, or configure an event subscription to receive a push when processing completes.
Key concepts
Organization — each API key is bound to one organization. All resources (files, jobs, runs, subscriptions) are scoped to it.
Files — documents stored in Plextera and referenced by fileId. Must be uploaded before use in jobs or workflows.
Document Insights — asynchronous extraction jobs that produce typed field values from a document. Jobs follow a QUEUED → PROCESSING → COMPLETED lifecycle.
Hubs — hub-configured extraction models and field schemas for a specific document type. Specify a hubId explicitly, or let Plextera route automatically.
Workflows — processing pipelines configured in Plextera Studio. Can include Document Insights steps, data transformation, and custom logic.
Event subscriptions — HTTPS webhooks that push notifications when jobs or runs reach terminal states.
Next steps
- Quickstart — process your first document end-to-end
- Authentication — how to authenticate requests
- Events — receive push notifications instead of polling
- API Reference — full endpoint reference with interactive examples