Veritura · Developer documentation

The documentation-evidence layer for compounded medicine

Veritura reads the paperwork behind a preparation: certificates of analysis, receiving records, releases: keeps the record, and makes it verifiable per unit. Every vial can carry a QR seal that resolves to a live, patient-readable record. These pages document how a pharmacy system integrates with that.

The boundary, stated once and everywhere: Veritura verifies documentation. It never tests material and never makes a safety, quality, or FDA-approval determination. Every surface in this documentation: the API, the label, the public pages: repeats this boundary, and integrations must not remove it.

The three hosts#

Host	What it serves
`www.veritura.co`	The workspace (operator sign-in) and the Platform API under `/api` and `/v1`.
`verify.veritura.co`	Only the public record pages: unit records (`/u/<serial>`), passport records (`/verify/<share>`), receipts, claims, and the patient space. Printed QR codes point here. This host serves nothing else, permanently.
`docs.veritura.co`	This documentation.

Start here#

QR Passport integrationFrom a certificate on file to a released, patient-scannable unit record: the full flow, including the pharmacist release for a pharmacy's own preparations, and the two integration modes. Platform API (v1)Key-authenticated endpoints for running checks, minting seal batches, downloading labels, and issuing passports from your own system. Seal label specificationThe 2.25 × 1.25 in thermal seal: exact geometry, ZPL, PDF formats, printer requirements, and what may never change on it. Patient record pagesWhat a scanned seal or a shared passport link actually shows: the public pages on verify.veritura.co and the states they can be in.

Authentication at a glance#

Two ways in, used by different callers: the full detail is on the authentication page:

Workspace session: an operator signed into www.veritura.co/app. All /api/… endpoints in the guides use this.
API key: server-to-server calls to /v1/… with Authorization: Bearer vk_live_… (or vk_test_… for sandbox records). Keys are created in the workspace under Settings and are shown once at creation.

# Every /v1 call:
curl https://www.veritura.co/v1/seal-batches \
  -H "Authorization: Bearer vk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"lot_id": "LOT-...", "count": 30}'

What a patient sees#

A scanned seal opens verify.veritura.co/u/<serial>: whether the vial is on record, whether anything is flagged on its batch, what the laboratory paperwork says, and who to call: in plain language, with an optional recall-alert email. A serial that was never issued, or was altered, does not resolve at all. Scanning sends Veritura nothing about the patient. The full walkthrough is in patient record pages.