Programmatic access to the ODVIX platform
The API is the developer entry point into the same platform behind PaperLabs, Flow, Verify and Sign. Submit structured data, trigger document generation, initiate workflows, create review and signature requests, and subscribe to status events through webhooks.
"template_id": "tpl_offer_letter",
"data": { "customer_name": "…", "company": "…" }
}
- · document.generated
- · workflow.completed
- · review.approved
- · signature.completed
Requests, events and platform actions
The API exposes conceptual entry points across the ODVIX platform. Every request is authenticated with scoped credentials, every state change emits an event, and every event can be delivered to an external system as a webhook.
Trigger platform actions from external systems
Submit a template identifier and structured payload to produce a finalised document through the PaperLabs engine.
Start a Flow workflow from an external event, providing the workflow identifier and trigger payload used by downstream steps.
Create a Verify review request against a generated document with reviewer routing and expected outcomes.
Create a Sign signature request with participants, ordering and reminders, bound to a specific document version.
Observe platform activity in real time
Every generation, workflow, review and signature action emits status events tied to a stable identifier for the parent resource.
Configure webhook endpoints to receive event payloads over HTTPS with signed delivery so consumers can verify authenticity.
Event and response payloads are JSON. Consumers can subscribe to a subset of event types per endpoint to keep integrations focused.
Scoped credentials and workspace boundaries
Issue API keys per workspace with defined scopes across generation, workflows, review and signature surfaces.
Webhook payloads are signed with a shared secret so consumers can verify that events originated from the ODVIX platform.
Requests and events carry stable identifiers so consumers can safely deduplicate retries and reconcile state.
How teams plan to use the API
Call the generation endpoint with a template identifier and structured payload, receive a document identifier, and use webhook events to deliver the finalised PDF back to the end user.
When a business event occurs internally, trigger the matching Flow workflow with the source payload and let the platform coordinate generation, review, signature and delivery.
Subscribe to document and workflow status events to write completed document references and workflow outcomes back into an operational database.
Generate proposals and orders directly from CRM records by posting opportunity payloads to the generation endpoint on demand.
Trigger Verify review requests and Sign signature requests from an external system and observe outcomes through webhook events.
Drive scheduled invoice generation from an existing billing system by calling the workflow trigger endpoint on the required cadence.
Works with the rest of the platform
Build with ODVIX API
Request Early Access to receive integration details, credentials and release updates as capabilities roll out.