WQ3 API is a way to use the same WQ3 platform within your existing systems. Evaluate the document workflow you need and consult the API documentation for supported operations.
Illustrative architecture, not a specification of endpoints or deployment. The WQ3 API belongs to the product; this website describes it.
Your application identifies the document and people involved.
Connect through WQ3 API and use embedded signing where appropriate.
Use webhooks to inform your application's document workflow.
Illustrative JSON only. The field names and identifiers are examples, not an API contract or executable request. No request is sent from this page. Consult the actual API documentation for endpoints, authentication, and supported payloads.
{
"document_id": "<illustrative_document_id>",
"recipients": [
{ "name": "Example signer", "email": "signer@example.invalid", "order": 1 }
]
}Explore where signing belongs within your application.
Connect business documents and signing steps to an existing system.
Evaluate a signing journey within your application experience.
Keep connected processes informed about document workflow activity.
Use the WQ3 API documentation as the implementation reference. Bring your document workflow requirements to an API inquiry.