API
A REST API to create documents, add signers, send for signature and download signed copies.
Features
WQ3 API
Connect your systems to WQ3 to create, send and track documents for signature.
Why teams use it
Start signing workflows from your existing systems.
Track status without manual checks.
Retrieve completed documents automatically.
Related
Embedded signing
Let users sign inside your own website, portal or application through the WQ3 API.
WQ3 API
Use WQ3 signing from inside your own applications and systems.
Planning an integration?
Tell us about your systems and we'll share API access details.
Define the handoff from your business process
Before development begins, identify the event that makes a document ready for signature: an internal approval, an accepted request or a completed review. Treat this as a business decision, not simply a technical operation. Your application should check the document version, signer details and required approvals before initiating the send step.
WQ3 locks documents once sent, so content review belongs before that boundary. Plan how your team will handle corrections discovered afterwards rather than assuming an active signing document can be edited. Keep a reference in your own system linking the business record to its corresponding document, so staff can distinguish versions and avoid confusion.
Translate contract requirements into signing policy
Define signing requirements for each document category before mapping them into application logic. WQ3 has exactly three signing levels: electronic signature, remote signing and token signing, with different levels available for different signers on the same document. This lets you plan around each participant’s role and the agreement’s requirements rather than applying one choice to everyone.
The eKYC add-on verifies an account; it is not a fourth signing level, and a verified account can be required with any level. Document when that verification is needed, then discuss how to apply these requirements through the API. Review legal choices with your advisers: Egypt’s E-Signature Law No. 15 of 2004 grants legal validity when its conditions are met, not merely because an API is used.
Make access boundaries clear in your application
When designing the signing experience, distinguish access to a user’s application account from access to their assigned document. WQ3 uses individual invitations and private signer links that show only what belongs to that signer. Your interface should make clear which document is being signed, who requested the signature and what the user is expected to do next.
WQ3 data travels over TLS 1.2 or newer, but the connected application also needs appropriate data-handling practices. Plan to protect API credentials, restrict staff access and avoid unnecessary logging of sensitive document content. Before implementation, request authentication details and embedded-signing requirements so your design follows the available integration guidance rather than assumptions about how access works.
Plan for evidence after completion
Decide what your system needs for retention and review after an agreement is complete, not just where the signed copy will be stored. Every completed WQ3 document comes with an audit trail and completion certificate recording its actions. Plan to associate this evidence with the original business record and define who may access it under your retention policy.
The public verification page provides another way to check authenticity without a WQ3 account. A QR code appears on the completion certificate and final file, while SHA-256 fingerprint comparison reveals changes to the signed file. During integration planning, confirm how to retrieve or access the certificate and audit trail rather than assuming a signed-copy download includes every supporting record.
REST API
Start integrating with one request.
Create a document, add signers, and follow every event from inside your application.
POST /v1/documents
{
"name": "contract.pdf",
"signers": [
{ "email": "sara@example.com" }
]
}Explore more
Related pages
Electronic signature
Let every signer sign business documents electronically from a secure invitation link, on any device.
Learn moreSend documents for signature
Send any business document for signature in a few steps and follow its progress until it is complete.
Learn moreMultiple signers on one document
Add every approver and signer a document needs, each with their own fields and role.
Learn moreSigning order
Define the exact order in which approvers and signers act, and WQ3 enforces it.
Learn moreDocument templates
Save the documents you send most often as templates with fields, roles and signing order ready.
Learn moreBulk send
Send the same document to many recipients at once, each receiving their own copy to sign.
Learn moreStart your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Is there a specified API authentication method?+
This page does not specify the authentication mechanism. Request API access details before choosing how your application will manage credentials.
Does the API support webhooks?+
Status tracking is described, but the update mechanism is not specified. Confirm notification and querying options before building status handling.
Can signers use different signing levels?+
Yes. WQ3 allows different levels for signers on the same document. Discuss how to configure these choices through the API during integration planning.
Is eKYC required for every signature?+
eKYC is an account-verification add-on, not a signing level. It can be required with any level when your process needs proof of the account holder’s identity.
Does a recipient need an account to verify a completed contract?+
No. The public check page allows authenticity verification using the QR code or reference without a WQ3 account.