Skip to main content
You do not have to store Blend UUIDs to use the Blend API. Almost every path parameter and product reference accepts your own identifier as an alternative, so your system can stay the source of truth for IDs. Set external_id when you create a patient or an order, map your sku and product_code onto Blend products during onboarding, and you can address Blend resources entirely in your own vocabulary.

What each resource accepts

Fetch an order by your own ID

The same path position accepts a Blend UUID or the human-friendly order number — you don’t need separate code paths for each.

Set your IDs at creation time

A patient’s external_id is also used for prescription matching. When you send an electronic prescription referencing external_id, Blend links it to the right patient without a name-and-date-of-birth lookup — which is the most reliable matching path available. See how Blend matches prescriptions to patients.
sku and product_code are not interchangeable. Non-prescription products and order materials can be referenced by Blend id or sku only; product_code is available for prescription products.
You can set or change external_id on an existing order with PATCH /orders/{order_id} — useful when your own record is created after the order reaches Blend. External IDs are editable in the Blend Dashboard.

Get an order's details

Accepts UUID, order number, or external ID

Get a patient's details

Accepts UUID or external ID

Update a prescription product

Set your sku and product_code