API
A REST API to create documents, add signers, send for signature and download signed copies.
Why teams use it
Create and send documents from your system.
Embedded signing for your users.
Receive signed results automatically.
Related
Integrations
Connect WQ3 to ERP, HR, CRM, productivity and storage systems, or build a custom integration.
WQ3 Dedicated
A private environment for WQ3 that we plan with you around your requirements.
What's included
REST API
Create documents, add signers, send and download signed copies.
Webhooks
Real-time events on every signing status change.
Embedded signing
Show the signing experience inside your own app.
How to start
Request API keys, try the API in the test environment, then move to production after review.
Common questions
Are the features the same in every option?
Yes. Cloud, API and Dedicated are different ways to use the same WQ3 platform.
Can we start with one and move later?
Yes. Many teams start on the cloud, then add the API or move to a dedicated environment.
Define workflow rules before building
Start by identifying the process your integration will serve: which business record needs a signature, who reviews the document, and when it becomes ready to send. WQ3 locks documents once sent, so place content approval and signer-detail checks before that boundary. This helps prevent signing from starting on a version your organisation has not approved.
Plan how your application will associate a document with its originating record, so authorised staff can find the right agreement without relying on filenames alone. Also define what your system considers complete and who handles discrepancies between internal records and signing status. These are application workflow decisions worth documenting alongside the integration design.
Translate signing policy into requirements
WQ3 allows a different signing level for each signer within the same document. When planning your integration, translate your organisation’s contract policy into explicit signer requirements rather than assuming everyone needs the same level. The three levels are electronic signature, remote signing and token signing; eKYC is an account-verification add-on, not a fourth level.
Agreement type can guide the choice: electronic signature for everyday agreements, and remote or token signing for formal, high-value contracts and stronger digital-signature requirements. Where account-holder identity must be established, treat eKYC verification as a separate requirement. Review these choices with legal and operational owners before turning them into automated rules in your application.
Design event handling around business records
Treat signing-status changes as inputs to your application’s workflow, not automatic proof that every related business task is finished. Decide which changes should update an internal record, notify a colleague or initiate a review. Keep a clear distinction between what happened in WQ3 and which follow-up actions your own system has completed.
As part of your integration design, plan for repeated notifications, temporary interruptions and events arriving after an internal process has moved forward. Confirm delivery and retry behaviour with the WQ3 team rather than assuming it. Test whether processing the same event again could duplicate an action in your system, and define a review path for discrepancies that cannot be resolved automatically.
Prepare for evidence retention and review
Plan to preserve signing evidence, not just the final file. Every completed WQ3 document has an audit trail and completion certificate; decide how your team will retrieve these alongside the associated business record. Establish internal access and retention rules appropriate to your organisation’s responsibilities and data-protection requirements.
The public verification page can support later review through the contract reference, QR code and SHA-256 file-fingerprint comparison. Make sure internal support procedures distinguish checking a file’s authenticity from assessing its legal sufficiency for a particular purpose. WQ3 is aligned with Egyptian E-Signature Law No. 15 of 2004, but legal validity depends on meeting applicable conditions, not simply on using an API.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Must every signer use the same level?+
No. Different signers can use different levels within one document; plan your integration around each party’s requirements.
Is eKYC an additional signing level?+
No. It verifies the account holder’s identity and can be required with any of the three signing levels.
When should final content checks happen?+
Before sending. Documents are locked once sent, so place content approval and signer-detail checks ahead of that step.
Should we retain more than the signed copy?+
Plan to retain the audit trail and completion certificate too, so reviewers can trace the signing actions.
Can a recipient verify a contract without a WQ3 account?+
Yes. Each signed contract has a public verification page accessible through its reference or QR code without an account.