OyeChats
FeaturesSolutionsIntegrationsPricingDocsBlogContact us

Works with your whole setup.

One script tag installs everywhere. Every event is sent straight to your CRM, automation tool, or analytics platform.

WordPress
Paste one script tag
Script
Webflow
Custom embed code
Embed
Next.js
Script component
Script
HTML / Vanilla
Single script tag
Script
Vue.js
Add the script tag
Script
React
Drop-in component
npm
Framer
Custom embed code
Embed
Calendly
In-chat booking
Link
Webhooks
5 event types
Webhook
REST API
Full OpenAPI spec
HTTP
Push events

Webhook setup in three steps.

OyeChats POSTs a signed JSON payload to your endpoint whenever a business event fires.

01

Add a webhook URL

In your OyeChats dashboard under Settings → Webhooks, paste the endpoint on your side that should receive events. HMAC secret is generated automatically.

02

Choose your events

Pick from five event types: tier_transition, lead_captured, handoff_requested, meeting_booked, chat_closed. Each fires once per business fact.

03

Verify the signature

Every request carries an X-OyeChats-Signature header (HMAC-SHA256 over the raw body). Reject anything that fails verification or is older than 5 minutes.

Chat event
OyeChats API
HMAC
Signed payload
Your endpoint

Example payload

JSONtier_transition
{
  "event": "tier_transition",
  "bot_id": 42,
  "timestamp": "2026-04-11T14:23:05Z",
  "data": {
    "session_id": "conv_8f3a2b1c",
    "lead": {
      "name": "Sarah Chen",
      "email": "sarah@acme.com"
    },
    "bant": {
      "budget": 82,
      "authority": 91,
      "need": 74,
      "timeline": 68,
      "composite": 79,
      "tier": "hot"
    }
  }
}
Signature verification. Every webhook request includes an X-OyeChats-Signature header (HMAC-SHA256 over the raw body). Verify it in your handler before processing. Reject any request more than 5 minutes old to block replay attacks.