Skip to content
QSign QSign Docs

Quickstart

This walks you through your first signing request with the QSign API. You’ll create an API key, send a document to a signer, and receive the signing link.

1. Get an API key

Section titled “1. Get an API key”

In the QSign Developer portal (app.qsig.in → Developers), generate a key. You get two:

  • a live key — qsk_live_… (production)
  • a sandbox key — qsk_test_… (simulated; no quota, no real emails or charges)

Keys are shown once on generation and stored only as a hash. Send your key in the X-Api-Key header on every call. Start with the sandbox key while you build — see Sandbox & testing.

2. Send a document for signature

Section titled “2. Send a document for signature”

POST /document/recipients/create/ creates a document and its signers in one call:

Terminal window
curl https://app.qsig.in/backend/othercompanyapi/document/recipients/create/ \
  -X POST \
  -H "X-Api-Key: qsk_test_…" \
  -H "Content-Type: application/json" \
  -d '{
    "doc_url": "https://example.com/nda.pdf",
    "document_name": "Mutual NDA",
    "recipientDetail": [
      { "name": "Jane Doe", "email": "jane@example.com", "type": "signer" }
    ]
  }'
Section titled “3. Get the signing link”

POST /document/signing-links/ returns the secure signing URL for each recipient — email it yourself, or let QSign send the invitation:

Terminal window
curl https://app.qsig.in/backend/othercompanyapi/document/signing-links/ \
  -X POST -H "X-Api-Key: qsk_test_…" -H "Content-Type: application/json" \
  -d '{ "doc_id": "<id-from-step-2>" }'

4. Track completion

Section titled “4. Track completion”

Poll GET /document/sign/status/?doc_id=<id>, or — better — register a webhook to be notified the moment the document is signed or declined. When everyone has signed, download the sealed PDF with GET /document/download/?doc_id=<id>.

Next steps

Section titled “Next steps”