> ## 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.

# How do I add a prescriber to Blend?

> POST /api/v1/prescribers with first_name, last_name, phone, npi, and at least one credential. If the NPI already exists in Blend, the existing prescriber is returned and associated with your account.

`POST /api/v1/prescribers` requires five things: `first_name`, `last_name`, `phone`, `npi`, and at least one entry in `credentials`. Everything else — addresses, DEA and SPI numbers, state licenses, supervisors — can be added at creation or later.

Prescribers must exist in Blend before their prescriptions can be filled. Blend imports them in bulk during onboarding; this endpoint is for the ones you add afterwards.

## Create one

```bash theme={null}
curl -X POST https://api.byblend.com/api/v1/prescribers \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "first_name": "Willard",
    "last_name": "Donnelly",
    "phone": "6417383445",
    "email": "wdonnelly@clinic.example.com",
    "npi": "1234567890",
    "dea": "F91234563",
    "spi": "1234567890ABCDEF",
    "credentials": [{ "credential_code": "MD" }],
    "addresses": [{
      "type": "practice",
      "address_1": "140 Lindgren Street",
      "city": "Boston",
      "state": "MA",
      "zip_code": "02108"
    }],
    "qualifications": [{
      "state": "MA",
      "license_number": "1234567890",
      "expiration_date": "2027-03-15"
    }]
  }'
```

* **`credential_code`** — pull valid values from `GET /api/v1/prescribers/credentials`.
* **`addresses[].type`** — `practice` or `working`.
* **`qualifications`** — state licenses; see [keeping prescriber licenses current](/guides/prescriber-licenses).

## If the prescriber already exists

<Note>
  Blend deduplicates on **NPI**. If you post a prescriber who already exists, the existing record is returned rather than an error. If they exist elsewhere in Blend but not yet under your account, they are associated with your account. Posting the same prescriber twice is safe.
</Note>

This makes the endpoint effectively idempotent by NPI — useful when syncing a roster where you can't easily tell what's already been sent.

## Restricting what a prescriber can prescribe

The `restrictions` array holds prescription product IDs the prescriber may **not** prescribe. Use it where your own policy is narrower than the prescriber's license.

## Supervisory relationships

Where a prescriber practises under supervision, record it per state:

```bash theme={null}
curl -X POST https://api.byblend.com/api/v1/prescribers/1234567890/supervisors \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{ "supervisor_id": "0227d1e5-ba9a-42b5-8fe2-38882aa65708", "state": "CA" }'
```

<Warning>
  A supervisor must hold a valid qualification in at least one state before they can supervise. Create their license first.
</Warning>

<Tip>
  The path accepts a **10-digit NPI** anywhere a prescriber UUID is expected — you don't need to store Blend IDs for prescribers at all. See [using your own IDs](/guides/your-own-ids).
</Tip>

Prescribers are also fully manageable in the Blend Dashboard under Prescribers, where clinical and compliance staff can add licenses, credentials, and supervisors without touching the API.

<CardGroup cols={2}>
  <Card title="Create a new prescriber" icon="user-doctor" href="/api-reference/prescribers/create-a-new-prescriber">
    POST /prescribers
  </Card>

  <Card title="Get all available credentials" icon="id-badge" href="/api-reference/prescribers/get-all-available-credentials">
    Valid `credential_code` values
  </Card>

  <Card title="Create a supervisorial relationship" icon="users" href="/api-reference/prescribers/create-a-supervisorial-relationship">
    Per-state supervision
  </Card>

  <Card title="Update a prescriber's details" icon="user-pen" href="/api-reference/prescribers/update-a-prescribers-details">
    PATCH /prescribers/{'{'}prescriber\_id{'}'}
  </Card>
</CardGroup>
