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

# Benefit verification webhooks

> Understand when benefit verification webhooks are sent.

The benefit verification flow determines medication coverage and whether a
prior authorization is required. It has one event type:
`benefit_verification.status_change`.

See [Webhooks](/api-reference/webhooks) to configure an endpoint and understand
the shared delivery envelope, signature verification, retries, and processing
guidance.

## When webhooks are sent

| Journey step                    | Webhook behavior                                                                                                 | What your integration should do                        |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| Create the benefit verification | No webhook is sent for request acceptance; the API responds synchronously.                                       | Store the returned benefit verification ID.            |
| Verification in progress        | No webhook is sent for each verification attempt.                                                                | Continue to treat the benefit verification as pending. |
| Terminal result                 | Develop Health sends `benefit_verification.status_change` when the verification reaches `completed` or `failed`. | Inspect the terminal status and results in `data`.     |

## `benefit_verification.status_change`

This event represents the terminal customer-facing result, not every attempt
made to obtain it. Inspect:

* `data.status`;
* `data.error` when the verification failed;
* `data.drugs` for coverage, PA requirements, and cost-sharing results;
* `data.patient_coverage_status`; and
* `data.pharmacy_benefit_manager_name`, `data.patient_plan_fund_source`, and
  `data.patient_coverage_type` when available.

The webhook's `data` object matches the resource returned in the `data` field
of
[GET /benefit-verification/{id}](/api-reference/medication-benefit-check/get_item).
Use that endpoint to retrieve the latest complete benefit verification.