Buzzbip Logo
LoginBook Demo
  1. Home
  2. Developer Hub
  3. Webhooks
  4. Webhooks
Search API docs, webhooks, SDK guides...
Developer Hub
  • Overview
  • Message Received
  • Message Sent
  • Message Failed
  • Contact Created
  • Contact Updated
  • Conversation Opened
  • Conversation Resolved
Help Center guide
Search API docs, webhooks, SDK guides...
Developer Hub
  • Overview
  • Message Received
  • Message Sent
  • Message Failed
  • Contact Created
  • Contact Updated
  • Conversation Opened
  • Conversation Resolved
Help Center guide
Webhooks6 min read · Updated 2026-06-01

Webhooks

Configure BuzzBip webhooks to receive real-time POST notifications for messages, conversations, and contact events.

Webhooks let your application receive real-time notifications when events occur in your BuzzBip workspace. Instead of polling the API, BuzzBip sends an HTTP POST request to your configured endpoint with a JSON payload describing the event.

How webhooks work

  1. An event occurs in BuzzBip (e.g. a contact sends a message)
  2. BuzzBip constructs a JSON payload and signs it with your webhook secret
  3. BuzzBip sends an HTTP POST to your endpoint URL
  4. Your server verifies the signature and processes the event
  5. Your server responds with 200 OK within 10 seconds

Configure webhooks

  1. Sign in at app.buzzbip.com
  2. Go to Settings → Developer → Webhooks
  3. Click Add Webhook and enter your HTTPS endpoint URL
  4. Select the events you want to subscribe to
  5. Save and copy the signing secret for payload verification

Supported events

EventDescriptionGuide
message.receivedA contact sends an inbound message/developers/webhooks/message-received
message.sentAn outbound message is delivered/developers/webhooks/message-sent
message.failedAn outbound message fails to deliver/developers/webhooks/message-failed
contact.createdA new contact is added to Audience/developers/webhooks/contact-created
contact.updatedContact fields or tags are updated/developers/webhooks/contact-updated
conversation.openedA new conversation is opened/developers/webhooks/conversation-opened
conversation.resolvedA conversation is marked resolved/developers/webhooks/conversation-resolved

Payload envelope

Every webhook delivery uses the same top-level structure. The data object varies by event type.

json
{
  "id": "evt_7f3a9b2c",
  "type": "message.received",
  "createdAt": "2026-06-01T14:32:00Z",
  "data": { }
}

Verify signatures

Each webhook request includes an X-BuzzBip-Signature header containing an HMAC-SHA256 hex digest of the raw request body, computed with your signing secret.

javascript
const crypto = require('crypto');

function verifySignature(rawBody, signature, secret) {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(rawBody, 'utf8')
    .digest('hex');
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected)
  );
}

Retries and idempotency

BuzzBip retries failed webhook deliveries up to 5 times with exponential backoff when your endpoint returns a non-2xx status or times out. Use the event id to deduplicate deliveries.

⚠

Your endpoint must use HTTPS with a valid TLS certificate. HTTP URLs are not accepted.

Message received webhook →

Need help with your integration?

Our team can help you design, build, and troubleshoot custom BuzzBip integrations.

Contact SupportBrowse Help Center

On this page

  • How webhooks work
  • Configure webhooks
  • Supported events
  • Payload envelope
  • Verify signatures
  • Retries and idempotency

Next-Gen AI-Powered Conversational Marketing for E-commerce

Meta

Official Meta Tech Provider

Product

  • Features
  • How It Works
  • Pricing

Company

  • About Us
  • Team
  • Contact

Resources

  • Blog
  • Case Studies
  • Support

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy

© Copyright 2025 BuzzBip. All rights reserved.