Webhooks deliver real-time notifications when events occur in your account. Common use cases include CRM integration, analytics pipelines, alerting, and triggering automated follow-up campaigns.Documentation Index
Fetch the complete documentation index at: https://docs.politicalcomms.com/llms.txt
Use this file to discover all available pages before exploring further.
Use cases
CRM integration
Update contact records when messages are delivered or fail.
Analytics pipelines
Stream click data to your data warehouse for analysis.
Alerting
Notify staff when constituents reply to messages.
Automation
Trigger follow-up campaigns based on engagement.
Five event types
message.sent- Message accepted by the carrier.message.delivered- Carrier confirmed delivery to the recipient’s device.message.failed- Carrier rejected the message or delivery failed.message.replied- Inbound SMS/MMS received from a contact.link.clicked- Recipient clicked a tracking link.
How webhooks flow
We POST the payload to your endpoint
Signed with HMAC-SHA256 over the JSON body, with headers identifying the event type, ID, and timestamp.
Your endpoint validates and acknowledges
Validate the signature, persist or queue the event for processing, and return
200 within 10 seconds.Where to go next
Set up an endpoint
Configure event subscriptions, copy your signing secret, and send a test webhook.
Validate signatures
HMAC-SHA256 validation pattern with a Node.js example.
Event payload reference
Full JSON samples for every event type.
Retry policy
Schedule, best practices, and how to make handlers safely idempotent.