Tracking and results

Once a document is out, check its status, read the activity history, and download the signed PDF and the certificate of completion when it's done.

Check for updates

The API doesn't send webhooks yet, so check for changes on a schedule:

• One document: GET /documents/{id} and read status and each recipient's status.
• Many documents: GET /documents?status=completed&created_after=… on a schedule, then download anything new.

Every few minutes is plenty for most apps. Signers usually take minutes or hours, not seconds.

// Every 5 minutes: download documents completed since the last run
const since = lastRun.toISOString();
for await (const d of allDocuments({ status: "completed", created_after: since })) {
  if (!alreadySaved(d.id)) await saveSignedPdf(d.id);
}

# Every 5 minutes: download documents completed since the last run
for d in all_documents(status="completed", created_after=last_run.isoformat()):
    if not already_saved(d["id"]):
        save_signed_pdf(d["id"])

created_after filters by when the document was created, so look back far enough to include documents that are still out. The allDocuments and all_documents helpers are on the conventions page.

Activity history

GET /documents/{id}/events lists everything that happened to a document, oldest first: sent, viewed, signed, reminders and more.

{
  "object": "list",
  "data": [
    {
      "id": "evt_k2m8q4",
      "object": "event",
      "type": "sent",
      "description": "Sent for signature",
      "actor": "api",
      "recipient_id": null,
      "created_at": "2026-11-09T15:04:05Z"
    }
  ],
  "has_more": false
}

Each event has an actor that says who did it: owner, api, recipient, system, admin, ai_claude or ai_chatgpt. Use description to show the history to a person, and type to act on it.

New types may be added, so show description for any you don't recognize.

Download the signed PDF

GET /documents/{id}/signed-pdf redirects (302) to a download link that works for 10 minutes. Request it again whenever you need a new link, and don't store the link itself.

curl -fL https://api.readyink.ai/v1/documents/doc_c9x1q8/signed-pdf \
  -H "Authorization: Bearer $READYINK_API_KEY" -o signed.pdf

const res = await fetch(`${BASE}/documents/${docId}/signed-pdf`, { headers });
if (!res.ok) throw new Error((await res.json()).error.message);
await writeFile(`${docId}.pdf`, Buffer.from(await res.arrayBuffer()));

res = requests.get(f"{BASE}/documents/{doc_id}/signed-pdf", headers=H)
res.raise_for_status()  # 409 not_completed until everyone has signed
open(f"{doc_id}.pdf", "wb").write(res.content)

Download the certificate

GET /documents/{id}/certificate works the same way and returns the certificate of completion, which records who signed and when.

Both downloads work only on completed documents. Otherwise you get 409 not_completed.

Verify a file

Each document has two SHA-256 hashes:

• version_hash: the document as it was sent.
• final_hash: the sealed, signed PDF.

To confirm a stored PDF hasn't changed, hash it and compare with final_hash. The signed copy is also stamped with readyink_id.

shasum -a 256 signed.pdf