> ## Documentation Index
> Fetch the complete documentation index at: https://docs.byblend.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Does Blend track prescriber license status for me?

> Yes, wherever it can. Blend auto-populates prescriber records from the national NPI registry, sweeps the DEA registry on a recurring basis for expired or inactive registrations, and holds orders when the prescriber isn't licensed in the state that matters.

Blend actively maintains prescriber credential data rather than treating it as static text you typed once. Records are populated from the national NPI registry, DEA registrations are checked against the federal registry on a recurring schedule, and state license coverage is evaluated at fill time — so an order does not ship against a prescriber who isn't properly licensed for that patient.

You remain responsible for supplying and renewing state licenses. Blend's job is to catch what's missing, expired, or inconsistent before it becomes a compliance problem.

## What Blend maintains automatically

<CardGroup cols={2}>
  <Card title="NPI registry population" icon="address-card">
    Prescriber demographics and professional credentials are pulled from the national NPI registry, so names, credential types, and practice details come from the authoritative source rather than manual entry.
  </Card>

  <Card title="DEA registry monitoring" icon="shield-check">
    Blend sweeps the federal DEA registry on a recurring schedule, flagging registrations that are expired, inactive, or absent from the registry entirely.
  </Card>

  <Card title="State license coverage" icon="map-location-dot">
    At fill time, Blend checks that the prescriber holds a valid license covering the patient's state. If not, the order is held rather than shipped.
  </Card>

  <Card title="Forward-looking refill risk" icon="calendar-check">
    Blend predicts when each prescription is next due and warns when the covering license expires before then — see [refill risk](/guides/refill-risk).
  </Card>
</CardGroup>

## What that means day to day

**Orders hold instead of shipping.** If a prescriber's license is missing or expired for the relevant state, the order moves to `exception` rather than going out the door. Supply or renew the license and the order releases automatically — no need to ask for a re-check. See [stuck orders](/guides/stuck-orders).

**Credential problems surface before a fill is due.** Rather than discovering an expired DEA registration when an order stalls, the recurring registry sweep raises it in advance.

**Duplicate manual entry is reduced.** Because prescriber records draw on the NPI registry, you generally don't need to key in credential details that are already public record.

## What you still need to supply

<Warning>
  **State licenses are yours to provide and renew.** Blend cannot obtain state board licenses on your behalf — there is no single national source for them. Add and renew them through the API or the Blend Dashboard; see [keeping prescriber state licenses current](/guides/prescriber-licenses).
</Warning>

Also yours: which prescribers belong to your account, any prescribing `restrictions` you want enforced, and supervisory relationships where a prescriber practises under supervision.

## Checking status yourself

```bash theme={null}
# Everything on file for a prescriber, by NPI
curl https://api.byblend.com/api/v1/prescribers/1234567890 \
  -H "Authorization: Bearer {access_token}"

# Which prescriptions are at licensing risk right now
curl "https://api.byblend.com/api/v1/prescriptions?refill_risk=true&page_size=200" \
  -H "Authorization: Bearer {access_token}"
```

The second call is the one worth running on a schedule. It returns `at_risk`, a reason code of `prescriber_unlicensed` or `prescriber_license_expiring`, and the dates behind the judgment — enough to build a prioritized renewal worklist.

<Tip>
  Prescriber records, licenses, and credential status are all visible in the Blend Dashboard under Prescribers. For compliance staff who don't work in the API, that's the day-to-day surface.
</Tip>

<CardGroup cols={2}>
  <Card title="Get a prescriber's details" icon="notes-medical" href="/api-reference/prescribers/get-a-prescribers-details">
    Licenses, credentials, restrictions
  </Card>

  <Card title="Get prescriptions" icon="triangle-exclamation" href="/api-reference/prescriptions/get-prescriptions">
    `refill_risk=true`
  </Card>

  <Card title="Create a license/qualification" icon="id-card" href="/api-reference/prescribers/create-a-licensequalification">
    Add or renew a state license
  </Card>

  <Card title="Get all available prescribers" icon="users" href="/api-reference/prescribers/get-all-available-prescribers">
    Audit your full roster
  </Card>
</CardGroup>