Event subscriptions let Plextera push product events to your webhook endpoint. Use them when your integration should react to completed, failed, or rejected processing without polling.
A common production pattern is: subscribe to terminal events, process webhook deliveries immediately, and periodically poll resources that have not completed after an expected time window.
Call POST /event-subscriptions with:
endpointUrl - the HTTPS URL Plextera should POST events to.eventTypes - one or more event types to subscribe to.signingSecret - a secret used to sign deliveries.filters - optional filters for workflow events, for example a specific workflow ID.The response omits filters when no filters are configured. Document Insights subscriptions usually do not need filters because the selected event types already define which extraction events are delivered.
Every event uses a common envelope:
The data field contains the event-specific payload. See the Event Reference for complete schemas and examples.
Every webhook delivery includes:
Each delivery is signed using the signingSecret you provided when creating the subscription. This confirms the delivery came from Plextera and that the payload was not modified.
Signature format:
Verification steps:
t and v1 from the header.<t>.<raw request body>.signingSecret.v1 using a constant-time comparison.The signing secret is write-only. Plextera never returns it in API responses. Store it securely and rotate it by updating the subscription with a new signingSecret.
2xx response marks the delivery as successful.2xx responses trigger retries with exponential backoff.eventId may be delivered more than once.eventId values or use your own deduplication key.