RumbleUp uses webhooks to notify your application in real time when events occur on the platform. When an event fires, RumbleUp sends an HTTP POST request with a JSON body to the endpoint URL you configure in your account dashboard under Integrations → Webhooks.

All events are sent via POST with a Content-Type: application/json header and JSON payload in the body.
Events are delivered over HTTPS.
If your endpoint is temporarily unavailable, the API will retry delivery for up to 24 hours.

Configuration

Navigate to Integrations → Webhooks in the RumbleUp portal.
Enter the URL of your webhook endpoint.
Select at least one event type to enable synchronization.
(Optional) Configure authentication:
- Provide both username and password for Basic Auth
- Provide only a username for Bearer token
- Example: entering 3PvwJaEg as username and leaving password empty will add:
  
  Authorization: Bearer 3PvwJaEg
(Optional) Set conditions (JSON format) to filter events. Example:

{ "flags": "special" }

This will only sync events where the contact has the special tag applied.

Payload Structure

All webhook events use the same top-level format:

Field	Type	Description
`type`	string	Event type identifier
`ctime`	integer	Unix Epoch time in milliseconds for when the event was sent
`data`	object	Event-specific payload (varies by event type)

Event Types

CONTACT_UPDATED — A contact record was created or updated
MESSAGE_RECEIVED — An inbound message was received
DELIVERY_RECEIPT — Message delivery status update
PROXY_PROVISIONED — A proxy number was provisioned
REPORT_CREATED — A report is ready for download