Document viewing, forms, generation, contracts and e-signature, each with its own API. Use them together, or add one to the application you already run.
Every product exposes its own API. Integration is loose, not tightly coupled, so you can adopt one product at a time.
Independent services
Each product runs as its own microservice. Drop VectorViewer into an app without taking on the rest of the suite.
Same API, either cloud
Build against SaaS, then move to a private cloud deployment in your own AWS account without rewriting the integration.
One API for each product.
The reference for VectorViewer, VectorForms and VectorGen is published below, with request and response examples you can try. The others are available on request.
Validates client credentials, looks up the document in DynamoDB, creates a viewer session (vid), and returns it along with document metadata. This is the API entry point for embedding the viewer.
Copies an existing form template and makes it available to a specific tenant, creating a new DynamoDB record with tenant scoping.
Responses: 200
POST/api/form/client/status
Get form submission status
Returns the current submission status and metadata for a specific form instance, including whether it has been submitted, saved as draft, or is still in progress.
Creates or updates a form session with pre-filled field values provided by the API caller, enabling pre-population of user data before the user opens the form.
Returns a map of all AcroForm field IDs to their properties for the specified form template, enabling API callers to understand the form schema before pre-filling.
Validates client credentials, looks up the form template, creates a form session (fid), sets session cookies, and redirects the user to the form renderer URL.
Returns a map of AcroForm field IDs to their display properties for the specified global form template. Used by API integrators to understand form structure before generating PDFs.
