Skip to main content
Every product reference in the Blend API accepts three forms of identifier, and you choose which to use:
  • id — the Blend product UUID
  • sku — your own inventory identifier
  • product_code — your own code, prescription products only
Map sku and product_code onto your Blend products during onboarding and your integration can speak entirely in your own vocabulary.

Which identifier goes where

product_code is available on prescription products only. Referencing a non-prescription product or an order material by product_code will not resolve — use sku.

In an order

Send exactly one identifier per line item — id, sku, or product_code, not several.

In a prescription

product_code is a shorthand helper to assist with matching from SCRIPT XML. Blend looks for product_code (and sku, product id, and name) in the <ProductCode>, <DrugDescription>, and <Note> XML fields.
Getting product_code right is the highest-leverage mapping you can do. It’s the top of Blend’s product-matching order and eliminates the guesswork of drug-name and description parsing — see how matching works.

Setting the mapping

This is a partial update — send only what’s changing. Non-prescription products and order materials have their own equivalent endpoints.

Listing what’s available

type accepts prescription, non_prescription, or order_material. There are also dedicated endpoints per type.
Blend sets up your initial catalog and maps it to your EMR or inventory system during onboarding — you shouldn’t need to map products one at a time to get started. Your product catalog is viewable in the Blend Dashboard under Products.

Get products

All types, or filter with type=

Update a prescription product

Set sku and product_code

Get prescription products

Just prescription products

Search products

By name or SKU