Skip to content
readback

Developers · REST API

Deposition transcripts from your own systems.

Send the ASCII, exhibits and signatures. Get back both PDFs with the acceptance verdict, and hear about it by webhook.

Create a transcript and wait for it
curl https://api.readbackhq.com/v1/transcripts \
  -H "Authorization: Bearer rb_test_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: quickstart-1" \
  -H "Prefer: wait=30" \
  -d '{ "source_file": "file_test_accepted" }'

What the API does

The same engine and quality gate as the app, over HTTPS with an API key.

  • Transcripts and renders

    Upload ASCII and exhibits, create a transcript, render with your options. Re-render without re-uploading.
  • The verdict, not just the PDF

    Every render says whether it was accepted, with a confidence score and stable warning codes.
  • Webhooks

    render.succeeded, render.needs_review and more, signed with Standard Webhooks and retried for about a day.
  • Built to retry safely

    Idempotency keys on every POST, cursor pagination, RFC 9457 errors and rate-limit headers.
  • Delivery to attorneys

    Cases, contacts and password-protected publications, with view and download receipts.
  • Wait or poll

    Prefer: wait=30 holds the request on standard renders; otherwise get a 202 and poll or wait for the webhook.

Try it in test mode

Test keys are free on every plan and never bill. Test renders are stamped TEST MODE, NOT FOR FILING.

A webhook delivery
{
  "id": "evt_...",
  "object": "event",
  "type": "render.succeeded",
  "livemode": false,
  "data": {
    "object": { "id": "rnd_...", "status": "succeeded" }
  }
}

Keys and plans

  • Test mode: every plan

    Create test keys in developer settings, including on Free.
  • Live keys: paid plans

    Live renders count exactly as in the app: once at first unlock, re-renders free.
  • SDKs: coming

    TypeScript and Python. Until then, any HTTP client and the OpenAPI document.

Get a free test key.

Free on every plan. Never bills.