Skip to main content
POST
/
webhooks
Webhooks Endpoint
curl --request POST \
  --url https://api.example.com/webhooks

​
What the Webhooks Endpoint Represents

The webhooks endpoint is the address your systems expose for Tuco to send event notifications. When you register a URL in Tuco:
  • Tuco uses that URL as the destination for selected events.
  • Your team stays in control of which environments and tools receive those notifications.
The system automatically handles when to call this URL based on the events you have enabled.

​
Types of Events You Can Receive

Depending on your configuration, Tuco can notify you about events such as:
  • New leads being added or updated.
  • Messages reaching a final visible state.
  • Availability or list changes that matter for outreach.
Each event notification is designed to be compact and focused on what changed, so your own systems can update their records without needing to know how Tuco performs its work internally.

​
High‑Level Payload Expectations

Although the exact fields may evolve over time, you can expect every webhook call to include:
  • A clear event type.
  • Enough identifiers to link the event back to your own data.
  • Timestamps that let you order events in your own logs.
Data is preserved safely in Tuco, so any identifiers you receive here can be cross‑checked in the Tuco UI or through the regular APIs.

​
Advanced Management APIs (Coming Soon)

Programmatic management of webhooks themselves (such as listing, updating, or testing webhook registrations via API) is Coming Soon. For now, focus on the behavior of the notifications your endpoint receives, and manage configuration from within the Tuco product where available.