How do I keep prescriber state licenses current?

A prescription can only be filled if the prescriber holds a valid license covering the relevant state. Add licenses with POST /api/v1/prescribers/{prescriber_id}/qualifications, giving at minimum a state and a license_number. Expired or missing licenses are one of the most common reasons an order gets stuck, so keeping this current is worth automating.

Add a license

curl -X POST https://api.byblend.com/api/v1/prescribers/1234567890/qualifications \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "OH",
    "license_number": "35-098765",
    "description": "Nurse Practitioner, Family",
    "expiration_date": "2027-03-15"
  }'

The prescriber path accepts a UUID or a 10-digit NPI.

Renew one without knowing its ID

Blend accepts a two-letter state abbreviation wherever a qualification UUID is expected, which resolves to that state’s currently-active license:

curl -X PUT https://api.byblend.com/api/v1/prescribers/1234567890/qualifications/OH \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "OH",
    "license_number": "35-098765",
    "expiration_date": "2029-03-15"
  }'

This means a renewal script needs only the NPI and the state — no Blend identifiers at all.

Updating a state’s license with a new number automatically deactivates the old one. You don’t need to deactivate the previous license first; the history is retained.

DELETE on a qualification deactivates it rather than removing it. Licensing history is preserved for compliance, so a deactivated license still appears in the record.

See what’s on file

curl https://api.byblend.com/api/v1/prescribers/1234567890 \
  -H "Authorization: Bearer {access_token}"

The prescriber record returns qualifications, credentials, addresses, and restrictions together.

Catching expiries before they cause a problem

Auditing expiration dates tells you which licenses lapse soon. It doesn’t tell you which ones matter soon. Refill risk does — it compares each prescriber’s license coverage against the predicted next fill date for each prescription:

curl "https://api.byblend.com/api/v1/prescriptions?refill_risk=true" \
  -H "Authorization: Bearer {access_token}"

A license expiring in three months is irrelevant if no fill is due; one expiring next week against a fill due Tuesday is urgent. Sort by days_until_next_fill, not by expiration date.

Blend also monitors prescriber credentials independently and flags problems it finds — see does Blend track prescriber license status for me?. Licenses are editable in the Blend Dashboard under Prescribers, which is where most compliance staff work.

Create a license/qualification

POST …/qualifications

Update a license/qualification

Accepts a state abbreviation

Deactivate a license/qualification

Soft-delete, history kept

Get a prescriber's details

All licenses and credentials

Guides

Getting started

Prescriptions

Patients

Orders

Prescribers

Products and catalog

Reporting and operations

How do I keep prescriber state licenses current?

Add a license

Renew one without knowing its ID

See what’s on file

Catching expiries before they cause a problem

Create a license/qualification

Update a license/qualification

Deactivate a license/qualification

Get a prescriber's details

​Add a license

​Renew one without knowing its ID

​See what’s on file

​Catching expiries before they cause a problem

Create a license/qualification

Update a license/qualification

Deactivate a license/qualification

Get a prescriber's details

Add a license

Renew one without knowing its ID

See what’s on file

Catching expiries before they cause a problem