mock_result.
You will create a benefit verification, retrieve it by ID, and interpret the
result. You need a terminal with curl and access to a sandbox organization.
1. Get a sandbox token
Ask your Develop Health contact for a sandbox organization, then create an API token for that organization. SetDEVELOP_HEALTH_SANDBOX_TOKEN to the token in your terminal environment.
Keep it on your server and out of source control.
2. Create a benefit verification
Save the following asbv-request.json. The NPI is illustrative; use your
configured sandbox test provider if your workflow requires one.
data.id. A successful response means the request
was accepted. The verification result is retrieved separately.
If the request is rejected, check the
response format and errors and the
BV error codes.
3. Retrieve the result
SetBV_ID to the data.id from the create response, then run:
data.status. If it is pending, wait a few seconds and retrieve the
same ID again. When it is completed, read data.patient_coverage_status
and each item in data.drugs.
For this mock scenario, each requested drug is covered, does not require prior
authorization, and has a copay. Inspect these fields in each drug result:
These are simulated benefits for integration testing. Do not use them to make
decisions about a real patient’s coverage. If the status is
failed, inspect
data.error; if it is cancelled, no coverage result is expected. See
statuses and error codes
for the complete lifecycle and result handling.
Next steps
- Create a benefit verification with your own request shape.
- Receive and verify webhooks to process results without repeated GET requests.
- Test in the sandbox with other coverage and failure scenarios.
- Create a prior authorization to try a prior authorization workflow.