Test statuses and webhook events
Trigger deterministic prior-authorization outcomes and inspect the signed webhook payloads.
Prior-authorization status changes are delivered to the HTTPS endpoint configured for your organization. Test requests use the same audit, outbox, signing, delivery, and retry path as live requests.
Test the receiver without patient data
Queue a signed prior_authorization.webhook_test event with an empty data object:
The response includes the event ID and a PENDING delivery status. GET /api/prior-authorizations/v1/webhook-endpoint reports the latest event’s attempt count, last HTTP status or error code, delivery state, and the total number of abandoned events.
After correcting a receiver, replay one abandoned event explicitly:
Only events in ABANDONED state can be replayed. A replay resets the retry counter and sends the same event ID and payload again, so receivers should continue deduplicating successfully processed events by webhook-id.
Trigger a test outcome
Create a prior authorization with test_mode: true. Test requests require valid, in-scope patient, coverage, provider, and facility IDs, but they are never submitted to a payer or added to Taiga’s review queue.
The create request first produces a prior_authorization.received event. Use the returned request id to trigger one of the supported test outcomes:
status must be NEEDS_INFORMATION, PARTIALLY_APPROVED, or DENIED. A terminal test outcome cannot be changed; create a separate test request for each terminal scenario. The endpoint is available in staging and production, but it rejects every request that was not explicitly created with test_mode: true.
Delivery headers
Every delivery includes:
Use webhook-id as the delivery idempotency key. Verify webhook-signature against the exact raw request body before parsing JSON. The signed content is:
The signature is HMAC-SHA256 encoded as standard Base64. The signing secret is returned when you configure or read your webhook endpoint.
NEEDS_INFORMATION
PARTIALLY_APPROVED
The test result approves half of the requested units on the first service line, rounded down with a minimum of one.
DENIED
Return any 2xx response after accepting an event. Failed deliveries are retried with exponential backoff and may be delivered more than once, so consumers must deduplicate by webhook-id.