From zero to your first signed contract in minutes.

From the dashboard, open Dashboard ← Developers ← API Keys and create a new key. You get two types of key, and there is no test mode — every key works on your real data immediately:

Authentication is performed through the header Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx with every request. Also pin the API version through the header Wthaiq-Version: 2026-07-01 so that the behaviour of the API stays stable across updates.

Our official first-class libraries are available for Node, Python and PHP, and they handle authentication, retries and API version pinning automatically. Or work with the API directly over cURL, without any package.

# cURL needs no SDK — just set your key
export WTHAIQ_API_KEY="sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

# Check connectivity by fetching the ready-made templates
curl https://wthaiq.com/api/v1/templates \
  -H "Authorization: Bearer $WTHAIQ_API_KEY" \
  -H "Wthaiq-Version: 2026-07-01"

npm i @wthaiq/node

import Wthaiq from '@wthaiq/node';
const wt = new Wthaiq('sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx');

pip install wthaiq

import wthaiq
wt = wthaiq.Client('sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx')

composer require wthaiq/wthaiq-php

$wt = new \Wthaiq\Client('sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx');

Now create a signature request from a ready-made template. In the following example we use the employment contract template (tpl_employment), and a single signer who signs by drawing their signature (method: draw) after identity verification is passed (require_identity: true), which raises the request to the advanced signature level (AES).

curl -X POST https://wthaiq.com/api/v1/signature_requests \
  -H "Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Wthaiq-Version: 2026-07-01" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 5f3c9c2e-..." \
  -d '{
    "title":"Employment contract — Ahmed M.",
    "source":{"type":"template","template_id":"tpl_employment"},
    "legal_level":"aes",
    "ordered":true,
    "signers":[
      {"name":"Ahmed Mohamed","email":"ahmed@example.com","type":"individual","method":"draw","require_identity":true,
       "fields":{"job_title":"Software Engineer","salary":"25000"}}
    ],
    "reminders":{"enabled":true,"interval_hours":48,"max":3},
    "metadata":{"order_id":"A-1024"}
  }'

const sr = await wt.signatureRequests.create({
  title: 'Employment contract — Ahmed M.',
  source: { type: 'template', template_id: 'tpl_employment' },
  legal_level: 'aes',
  ordered: true,
  signers: [
    { name: 'Ahmed Mohamed', email: 'ahmed@example.com', type: 'individual',
      method: 'draw', require_identity: true,
      fields: { job_title: 'Software engineer', salary: '25000' } }
  ],
  reminders: { enabled: true, interval_hours: 48, max: 3 },
  metadata: { order_id: 'A-1024' }
});

console.log(sr.signers[0].signing_url);

sr = wt.signature_requests.create(
    title='Employment contract — Ahmed M.',
    source={'type': 'template', 'template_id': 'tpl_employment'},
    legal_level='aes',
    ordered=True,
    signers=[
        {'name': 'Ahmed Mohamed', 'email': 'ahmed@example.com', 'type': 'individual',
         'method': 'draw', 'require_identity': True,
         'fields': {'job_title': 'Software engineer', 'salary': '25000'}}
    ],
    reminders={'enabled': True, 'interval_hours': 48, 'max': 3},
    metadata={'order_id': 'A-1024'},
)

print(sr.signers[0].signing_url)

$sr = $wt->signatureRequests->create([
    'title' => 'Employment contract — Ahmed M.',
    'source' => ['type' => 'template', 'template_id' => 'tpl_employment'],
    'legal_level' => 'aes',
    'ordered' => true,
    'signers' => [
        ['name' => 'Ahmed Mohamed', 'email' => 'ahmed@example.com', 'type' => 'individual',
         'method' => 'draw', 'require_identity' => true,
         'fields' => ['job_title' => 'Software engineer', 'salary' => '25000']],
    ],
    'reminders' => ['enabled' => true, 'interval_hours' => 48, 'max' => 3],
    'metadata' => ['order_id' => 'A-1024'],
]);

echo $sr->signers[0]->signing_url;

Response is an object signature_request with status sent, and contains the signer together with the signing link signing_url ready to open or embed:

{
  "id": "sr_3n8Kd2Qa1V",
  "object": "signature_request",
  "livemode": false,
  "status": "sent",
  "title": "Employment contract — Ahmed M.",
  "legal_level": "aes",
  "format": "pades-lt",
  "source": { "type": "template", "template_id": "tpl_employment" },
  "ordered": true,
  "require_identity": true,
  "reference": null,
  "reminders": { "enabled": true, "interval_hours": 48, "max": 3 },
  "expires_at": 1755000000,
  "completed_at": null,
  "download_url": null,
  "metadata": { "order_id": "A-1024" },
  "created_at": 1754000000,
  "signers": [
    {
      "id": "sgr_9fA2",
      "object": "signer",
      "name": "Ahmed Mohamed",
      "email": "ahmed@example.com",
      "type": "individual",
      "method": "draw",
      "require_identity": true,
      "order": 1,
      "status": "sent",
      "signing_url": "https://sign.wthaiq.com/s/uZ8..",
      "identity": { "status": "pending", "provider": "didit", "level": "aes" }
    }
  ]
}

There are two ways to know when the other party signs. Choose manual polling for quick experiments, and Webhooks for production.

Method one — polling: Query the request whenever you like. The status status reflects the latest state.

curl https://wthaiq.com/api/v1/signature_requests/sr_3n8Kd2Qa1V \
  -H "Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Wthaiq-Version: 2026-07-01"

Method two — Webhook: The full event body reaches you through POST to your endpoint, and the affected resource is wrapped under data.object:

{
  "id": "evt_2M",
  "object": "event",
  "type": "signature_request.completed",
  "created_at": 1754500000,
  "livemode": false,
  "data": {
    "object": {
      "id": "sr_3n8Kd2Qa1V",
      "object": "signature_request",
      "status": "completed",
      "legal_level": "aes",
      "reference": "WTQ-000123",
      "completed_at": 1754500000,
      "download_url": "https://wthaiq.com/api/v1/signature_requests/sr_3n8Kd2Qa1V/download"
    }
  }
}

Verify the signature header Wthaiq-Signature on every incoming request, and return the response 2xx quickly, and run the heavy work asynchronously.

As soon as the status becomes completed, download the final signed and sealed PDF file. This endpoint is available only for completed requests and returns application/pdf. The independent cryptographic evidence for this path is the sealed evidence record (JSON), not a PAdES signature embedded inside the PDF — download it through GET /api/evidence.php?scope=api&doc=<id>.

curl -L https://wthaiq.com/api/v1/signature_requests/sr_3n8Kd2Qa1V/download \
  -H "Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -o contract-signed.pdf

To verify the contract's integrity publicly, use Reference code WTQ-... assigned on completion. Any party holding the reference can confirm the document's authenticity and integrity — programmatically or through the public page ‎/verify‎.

curl https://wthaiq.com/api/v1/verifications/WTQ-000123 \
  -H "Authorization: Bearer sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

# Response
{
  "object": "verification",
  "reference": "WTQ-000123",
  "found": true,
  "status": "completed",
  "integrity": "intact",
  "document": { "title": "Employment contract", "sha256": "a3f1..", "format": "pades-lt", "legal_level": "aes" }
}