Developers

Add electronic signing to your application

One API that sends contracts for signature, tracks their status in real time, and returns the signed file to you — under your own brand. Start with a single key and pay as you go in Egyptian pounds.

How does the API work?

Four steps from your key to a signed contract in your account — without building any signing interface.

1

Create your key

from your account: a secret key sk_ for the server, or a console key pk_ for the browser.

2

Send a signature request

A single call with the contract and the signer's details; we fill in the fields and send the invitation.

3

Follow in real time

A signed Webhook that reaches your server on opening, signing and completion.

4

Receive the file

The signed contract plus a reference number and an audit trail for public verification.

POST /api/v1/signature_requests
# Send a contract for signing in a single call
curl -X POST https://wthaiq.com/api/v1/signature_requests \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "source": { "type": "template", "template_id": "tpl_265" },
    "signers": [{ "name": "Mohamed Ahmed", "email": "m@example.com" }],
    "fields": { "amount": "15000" },
    "legal_level": "ses"
  }'
  • A single key, no OAuth. Just a Bearer header — integration in minutes, not weeks.
  • A console ready to embed. Two lines on your site and it works — with no interface to build.
  • Legal standing. SES, AES and QES levels, signer identity verification, and a full audit trail.
  • Under your own brand (White-label). Your logo and colour on the signing page that the signer sees.
  • Signed Webhooks + a request log. Full diagnostics for your integration from your account dashboard.

Pay as you go — in Egyptian pounds

No annual subscription and no seat minimum. You pay only when you send each signature request.

See pricing