Event Reference
The Event Reference documents webhook payloads delivered by Plextera to endpoints configured through Event Subscriptions.
How events are delivered
Plextera sends an HTTP POST to your endpointUrl with a JSON body and standard headers.
Every delivery is signed with the server-generated signingSecret returned when you create the subscription.
See Verifying signatures.
Plextera records one immutable event per source event and creates one automatic delivery for each matching active subscription. If a document extraction is reprocessed after a terminal state, a later terminal state can produce a new event.
Common envelope
All events share the same top-level structure:
Document Insights events
Document Insights events use the same extraction structure returned by GET /document-insights/extractions/{extractionId}. Completed events include output; failed and rejected events include error.
document-insights.extraction.completed
Delivered when a Document Insights extraction reaches COMPLETED.
document-insights.extraction.failed
Delivered when a Document Insights extraction reaches FAILED.
DOCUMENT_NOT_ROUTED means no workspace configuration matched; verify labels.docType or default routing before retrying.
DOCUMENT_EXTRACTION_FAILED means processing or extracted-data validation could not complete and may be retried with backoff when the cause is temporary.
document-insights.extraction.rejected
Delivered when a Document Insights extraction reaches REJECTED.
Rejection occurs when the document cannot be accepted, for example because it is broken, empty, duplicate, uses an unsupported format, or uses an unsupported language.
Read error.message for the document-specific reason.
Workflow events
workflow.run.completed
Delivered when a workflow run reaches COMPLETED. The data payload includes the full run state, step-level outputs, and nested run summaries where applicable.
steps[*].output is passed through from Plextera Studio, so its property names and enum casing are step-specific. Internal values such as APPLICATION_PDF may appear there and are not normalized. For document_insights steps, treat extractionId as the stable correlation field and use the Document Insights extraction endpoint for the canonical, typed result.
workflow.run.failed
Delivered when a workflow run reaches FAILED or CLOSED. For FAILED, the
data.error field describes the failure. A run closed in Plextera Studio can omit
data.error; use data.status and data.steps to understand its last known state.