Skip to main content
This guide is for health plans. It covers how Scan labels those referrals when you read them back — not a separate create body. Before using this guide you need a sandbox and an access token. Request keys from Get API keys. How to send Authorization is in Authentication. Use synthetic data only on the initial sandbox. Listing imaging centers, searching or creating practices or law firms, and submitting an order-form-only referral may be off until Scan enables them for your account.

​
Create

POST /api/v2/referrals does not set line_of_business: health_plan today. The create endpoint does not currently accept member-ID or payer-ID fields. Send only fields documented in Creates a referral. Scan may enable a dedicated health-plan create schema in the future. To submit imaging in the meantime, use Submit a medical referral. Optional add-ons: Submit medical questions and Submit preferred times. Full intake: Submit for scheduling.

​
Identify a health-plan referral

On GET /api/v2/referrals/{referral_id} and on the status changed webhook nested referral:

​
Status changes

Every status, what it means, and how changes reach you are on Track referral status. One thing is specific to health plans: a visit sits in pending_auth while coverage is reviewed, which can delay booking. Do not poll for the internal steps in between — wait for the next webhook or take a snapshot when you need one.