AsyncAPI channel · Develop Health
· Develop Health Webhooks
/
Subscriber-hosted endpoint that receives Develop Health event POSTs.
Channel address
/
Operations
receive
receiveWebhook
Receive a Develop Health event notification.
Messages
benefit_verification.status_change
Benefit Verification Updated
Content-Type:
application/jsonprior_authorization.status_change
Prior Authorization Updated
Content-Type:
application/jsonprior_authorization.activity_log_updated
Prior Authorization Activity Log Updated
Content-Type:
application/jsonprior_authorization.message
Prior Authorization Message
Content-Type:
application/jsonprior_authorization.prescription_transfer_change
Prior Authorization Prescription Transfer Updated
Content-Type:
application/jsonprior_authorization.real_time_benefits_check_change
Prior Authorization Real-Time Benefits Check
Content-Type:
application/jsonAbout AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.