Webhook + Bento

Overview

The webhook endpoint is the fastest way to get custom purchase events, lifecycle milestones, or internal signals into Bento when the browser script or SDKs are not available.

• Send real-time JSON payloads that update subscriber timelines and lifetime value.
• Keep disparate systems (POS, back office, custom apps) in sync without standing up a full integration.

Requirements

• Copy the Site UUID for the workspace that should receive the events.
• Generate API credentials if you plan to sign requests yourself (optional but recommended).
• Prepare an HTTPS-capable client (server code, Zapier/Make HTTP modules, etc.).

Configure the webhook URL

Use the template below and replace replace_this_with_your_real_site_uuid with the UUID from System → API Keys. The trailing generic segment helps you identify the source in Bento; feel free to swap it for a descriptive value.

https://track.bentonow.com/webhooks/replace_this_with_your_real_site_uuid/generic/track

Recommended payload

Bento accepts a JSON body with an events array. Each event supports the same fields used by the public Events API:

{
  "events": [
    {
      "type": "purchase_completed",
      "email": "customer@example.com",
      "details": {
        "order_id": "ORD-12345",
        "total": 149,
        "currency": "USD"
      },
      "fields": {
        "first_name": "Avery",
        "lifetime_value": 984
      }
    }
  ]
}

Send the request as POST with the Content-Type: application/json header. If you need authentication, wrap the webhook behind your own middleware or add an Authorization header that your server verifies before relaying the payload to Bento.

Delivery tips

• Retries: retry on 429 and 5xx responses. Exponential backoff (e.g., 1s → 2s → 4s) protects against spikes.
• Logging: log both the payload and the Bento response so you can trace misformatted events.
• Segmentation: use different final path segments (/generic/, /pos/, /billing/) to identify multiple sources inside Bento timelines.

How the connection works

Every payload you post is queued immediately in Bento, associated with the subscriber identified by email, and exposed to:

• Automation triggers (Flows, Journeys, transactional logic).
• Lifetime value and revenue dashboards.
• Segments and filters inside the shared inbox.

Webhooks are ideal when you own the backend system and need deterministic, server-side event delivery without embedding additional SDKs.***