Get a demo

Solutions

Your systems stay in sync

The AutoRx API is queue-based. Webhooks are how you close the loop — no polling required.

  • No setup fee
  • Live in 1–2 weeks
  • PHIPA compliant
  • Canadian data residency

Why webhooks

Kroll writes are asynchronous — a prescription is queued and processed in the background. Your downstream systems (EHR, ops tooling, reconciliation software, banner platforms) need to know when a write completes without sending repeated status queries. Webhooks push that signal to you the moment it happens.

Events AutoRx sends

  • rx.completed

    The Kroll write succeeded. Includes patient identifier, queue ID, and the DIN written.

  • rx.failed

    The write failed permanently after retries. Includes the failure reason and the original queue ID.

  • rx.excepted

    The prescription was routed to the human review queue. Fires when exception occurs, not when it's resolved.

  • rx.resolved

    A human reviewed and approved the exception; Kroll write has now completed.

Delivery and reliability

AutoRx delivers webhooks with at-least-once semantics. If your endpoint is unreachable or returns a non-2xx response, AutoRx retries with exponential backoff over 24 hours. Each delivery attempt includes a timestamp and attempt number in the payload, so your system can deduplicate if needed.

Payload structure

All webhook events use a consistent envelope.

event

Event type string — e.g. rx.completed.

id

Unique event ID for deduplication across retries.

queueId

The intake queue ID returned when the Rx was first submitted.

timestamp

ISO 8601 UTC timestamp of when the event fired.

data

Event-specific payload — differs per event type.

Security: signature verification

Every webhook delivery includes an X-AutoRx-Signature header — an HMAC-SHA256 signature of the raw payload body using your webhook secret. Verify this header on your end before processing any event. Details are in the developer documentation.

Configuring endpoints

Webhook endpoints are configured per account in the dashboard. Banner and multi-site accounts can configure shared endpoints (all events from all sites) or per-site endpoints. Multiple endpoints per event type are supported. For the full payload schema and integration examples: /developers.

Get started with AutoRx

Ready to automate?

Most pharmacies go live within 1–2 weeks. No waitlist, no setup fee, and your existing Kroll setup stays exactly as-is.

Talk to us

Usually responds same business day