APIs
The share request is asynchronous: the first call returns a
request_id, and the token comes back on the second call once the facility responds. The response carries HIP details, token expiry, and whether the token should be displayed to the patient.
Scan & Share overview →
The HIP side of Scan & Share — receiving a scanned token at the facility counter — is a different integration. If your product also runs the facility’s software, see On-Share and the Scan and Share Token Received webhook.
M1 — ABHA Web SDK
Scan & Share is also available as a drop-in SDK component, including the QR scanner.

