API Terms of Use
Version 5 October 2026
Last updated: 5 October 2026
Effective date: 5 October 2026
Chapter One: General Provisions
1. Introduction and Scope
These API Terms of Use (the "Terms") govern the use of the developer console at developers.wthaiq.com, the application programming interface (API), the software development kits, the automated event notifications (webhooks), embedded signing, and every other service that Wthaiq provides for programmatic integration (the "API Services").
These Terms are read together with the Terms and Conditions of Use, the Privacy Policy, the Data Processing Agreement, the Acceptable Use Policy and the Electronic Signature Policy. In the event of a conflict on any matter concerning the API Services, these Terms prevail.
Creating a developer account or using any of the API Services constitutes acceptance of these Terms.
2. Definitions
- Developer account: the account created in the developer console to use the API Services.
- Account holder: the person who created the developer account in their own name or in the name of the company they represent.
- Members: the persons whom the account holder invites to the developer console to work on their account.
- API key: the secret credentials that the account holder's system uses to access the API.
- Test mode: use with test keys for trial and development purposes.
- Live sending: a signature request created with a live key and sent to real signers.
- Send: one signature request, whatever the number of signers in it.
- Plan: the annual subscription that sets the annual send allowance, the available capabilities and the number of members.
- Wallet: a prepaid balance from which sends beyond the plan allowance and identity checks are charged.
- Signer: every person to whom a signature request is sent through the API Services.
3. Independence of the Developer Account
The developer account is separate from Wthaiq platform accounts and is not linked to them in sign-in, data or balances. It is created with an email address that is not registered on the Wthaiq platform.
The account holder is responsible for the accuracy of the information provided at registration and for everything that takes place in the account, including the acts of the members they invite.
Chapter Two: Access and Verification
4. API Keys
The account holder undertakes to keep API keys strictly confidential, not to place them in code that loads in a browser or a public application, and to rotate them immediately on any suspicion of exposure.
Every request received with a valid key is deemed to have been issued by the account holder, who bears its consequences and charges, unless the account holder notified the Platform of the key's exposure before it was used.
5. Test Mode
Test mode is available free of charge on every plan, within daily limits per account: 20 test requests, 50 emails, at most 5 signers per request, and at most 10 recipients per bulk send. Identity verification is simulated rather than performed, and no WhatsApp messages are sent. Signature requests created in test mode are for trial purposes only, are marked as test requests, carry a test watermark on their documents, carry no legal effect, and must not be used in real transactions.
6. Live Sending and Company Verification
Live sending is available only when two conditions are met: an active paid plan and a verified company.
Company verification requires the documents that the Platform specifies, such as the commercial register, the tax card and the representative's authorisation, together with confirmation of the representative's identity. The account holder confirms that the documents and information provided are accurate, and that the Platform may refuse the verification request or withdraw the verification whenever it finds that any of them is inaccurate or that the representative's capacity has ended.
7. Technical Limits and Fair Use
The API Services are subject to technical limits on the number of requests per unit of time, and the Platform may slow down or temporarily refuse requests whenever they exceed these limits or threaten the stability or security of the service.
Chapter Three: Plans and Fees
8. Annual Plans
Paid plans are annual, and each has an annual send allowance that starts on the subscription date. Any part of the allowance not used during the year does not carry over to the following year. The available capabilities and the number of members vary according to the plan, as set out on the pricing page.
A paid subscription made through a payment provider that supports automatic renewal renews every year unless the account holder cancels the renewal before its date. A paid subscription made with a card that does not support automatic renewal receives reminders before it ends and is renewed with a new payment.
If the year ends without renewal, live sending stops and test mode remains available.
9. Upgrades and Downgrades
On an upgrade to a higher plan, the remaining value of the current plan is credited to the account holder and a new year starts on the upgrade date. A downgrade to a lower plan takes effect at the end of the current year, and once it takes effect the capabilities not included in the new plan are no longer available.
10. The Wallet
- Once the annual send allowance is used up, each additional send is charged to the wallet at the overage price announced for the account holder's plan.
- Each identity check is always charged to the wallet, at the price announced at the time of sending.
- The wallet is topped up with a minimum amount announced by the Platform, and its balance does not expire over time.
- Each account has a single wallet currency, set at the first payment, whether a plan subscription or a wallet top-up, being the currency stated in the price list displayed to the account holder at the time of purchase. This currency does not change once set, and the stored balance is never converted into another currency. Where the wallet is topped up through a payment method that charges in another currency, the amount shown in the wallet currency at the time of payment is added to it.
- If the wallet balance is not sufficient for an additional send or an identity check, the request is refused and the account holder is notified that the balance is low.
11. No Refunds
Plan fees and wallet top-ups are non-refundable. A send is counted against the annual allowance or the wallet as soon as the request is sent to the signers, even if it is cancelled afterwards, unless the invitation could not be delivered to any of them, in which case its value is returned to its source.
12. Delivery by WhatsApp
Sending signing links and verification codes by WhatsApp is currently available without additional charges, and the Platform may change this with prior notice.
13. Prices and Invoices
The prices announced at the time of payment apply. Invoices and taxes are subject to the Subscriptions and Billing Policy, and the Platform may change plan prices for the following years with prior notice.
Chapter Four: Data and Responsibilities
14. Data Roles
The account holder is the controller of the signers' personal data that it sends through the API Services, and the Platform processes that data on its behalf in accordance with the Data Processing Agreement.
The account holder confirms that it has a lawful basis for sending this data, and that it has provided the signers with the information required under the applicable law.
15. Retention of Documents and Evidence
The Platform keeps the document's digital fingerprint, the certificate of completion and the event log permanently, because they are the basis for verifying the signature.
If the account holder enables delivery to its external storage, the Platform may delete the signed document file from its servers thirty days after the signing is completed, once its delivery to the account holder's storage and its receipt by the signers have been confirmed. The deletion is recorded in the audit log, and verification of the signature remains possible.
16. Content and Acceptable Use
The account holder undertakes not to send through the API Services any documents that breach the law or the Acceptable Use Policy, and not to use the services for harassment, fraud or impersonation.
17. Electronic Signature and Its Evidential Weight
The Platform provides electronic signature tools and an evidence record. The evidential weight of a signature depends on the applicable law and on the signature level used, as set out in the Electronic Signature Policy.
Chapter Five: Suspension and Termination
18. Suspension
The Platform may suspend the API Services in whole or in part in the event of a breach of these Terms, a risk to the security of the service or to signers, or the withdrawal of the company verification.
19. Termination
The account holder may close the account at any time. Closing the account does not entitle the account holder to a refund of the plan fees or of the wallet balance. Data is handled after closure in accordance with the Data Retention Policy, and the evidence needed to verify past signatures is kept.
Chapter Six: Final Provisions
20. Limitation of Liability
The limitation of liability and disclaimer of warranties provisions in the Terms and Conditions of Use apply to the API Services.
21. Changes to These Terms
The Platform may amend these Terms and will notify account holders of material changes by email or through the developer console. Each version is kept in the Platform's legal archive, and continued use after an amendment takes effect constitutes acceptance of it.
Governing Law and Jurisdiction
This document shall be governed by and construed in accordance with the laws of the Arab Republic of Egypt, and the competent Egyptian courts shall have jurisdiction to determine any dispute arising out of it or relating to it, and any arbitration — should the two parties agree upon it — shall be conducted within the Arab Republic of Egypt and in accordance with its laws, without prejudice to any mandatory rights afforded to the User under the applicable laws of the User's country of residence.