The sandbox environment includes special-case inputs and predefined provider test data that allow developers to simulate edge cases during integration testing. See the list below for available scenarios:

This page documents test scenarios for various API endpoints to support validation and debugging of behaviors in different input cases. All endpoints are assumed to return standard HTTP response codes alongside expected JSON structures unless otherwise noted.

Same error test cases as above.

Same error test cases as above.

Sends one signed sample appointment webhook to webhook_url, signed with webhook_key, and returns the body it sent. Requires the external.appointment.read scope. Returns 404 outside Sandbox.

Every sample uses appointment_id 62g4ar44-1yv9-0931-dl3t-e9c2174kks09. The updated sample uses practice_id pt_1234.

Sends one signed sample insurance reference-data notification to webhook_url, signed with webhook_key, and returns the notification it sent. Any authenticated token works. Returns 404 outside Sandbox.

Every sample uses event_id evt_4f2c8a91d0b34e6f8a1c7d5e9b0f2a63. Only event_time_utc changes between calls.

A 200 means Zocdoc sent the request, not that your endpoint accepted it. Redirects are not followed.

Verify the signature against the raw bytes your endpoint received. The response can differ from the signed body in key order and null fields.