Skip to main content

eCourtDate Document Generation API guides

The eCourtDate Document Generation API generates court-ready PDF documents: reusable, versioned templates with merge tags, one-off documents from blank pages or HTML/CSS, image assets, batch jobs, and a per-account audit trail.

These guides explain the concepts and workflows; the interactive API reference documents every endpoint, request, and response, and includes a try-it console.

Base URL: https://api.pdfs.ecourtdate.com/v1

Start​

  • Getting started: create a key, generate your first PDF, publish your first template.
  • Authentication: API keys from the eCourtDate Console, scopes, and actor attribution.
  • Conventions: coordinates, pagination, limits, and the rules every request shares.

Templates​

  • Templates and versions: the immutable version lifecycle (draft → ready → published → superseded).
  • Merge tags: declare the data a template accepts; strict and lenient validation; dry runs.
  • Fields: the nine field types, from text and checkboxes to barcodes, tables, and HTML boxes.

Generating​

  • Generating documents: render from templates or one-off requests; binary and JSON responses; outputs and download URLs.
  • HTML documents: author documents in HTML/CSS with real layout and pagination; accessible tagged PDFs.
  • Batch generation: up to 200 documents per job, with per-item status and polling.
  • International text: Unicode rendering, script coverage, and right-to-left text.
  • Document options: PDF metadata, print scaling, watermarks, and page numbers.

Reliability and operations​

  • Errors: RFC 9457 problem+json and the stable error code registry.
  • Warnings: the warn-and-skip rendering model and the warning code registry.
  • Idempotency and retries: safe retries that can never duplicate a document.
  • Security: key handling, data lifecycle, sandboxed rendering, and the audit trail.
  • Versioning: the /v1 stability commitment and how the API evolves.

Resources​