MeetOne can deliver real-time HTTP notifications ("webhooks") to your integration whenever events happen in the system — for example, when a room is closed or a participant joins a video call.
What are MeetOne webhooks?
You create one or more webhook endpoints in the MeetOne admin. Each endpoint subscribes to one or more event types. When a subscribed event occurs, MeetOne sends an HTTP POST request with a JSON body to the endpoint's URL, signed with an HMAC-SHA256 signature derived from a secret unique to that endpoint.
Your integration verifies the signature, reads the payload, and reacts however it needs to — updating a record, triggering a downstream process, and so on.
Webhooks are enabled per MeetOne instance. If you don't see the Webhooks option in your admin sidebar, contact support to have it enabled for your organization.
Configuring a webhook endpoint
- Sign in to the MeetOne admin area.
- Navigate to Webhooks in the sidebar.
- Click New Webhook.
- Fill in the endpoint details:
| Field | Description |
|---|---|
| Name | Optional human-readable label shown in the endpoint list and delivery history. Falls back to the URL if left blank. |
| Status | Enabled starts delivering immediately. Disabled keeps the endpoint configured but skips delivery. |
| URL | The HTTPS endpoint that will receive deliveries. Must be publicly reachable from MeetOne's servers. |
| Events | One or more event types to subscribe to. See the event reference for the full list. |
- Click Save webhook. A signing secret is generated automatically when the endpoint is created.
- On the endpoint's detail page, copy the Signing Secret. Your integration needs it to verify incoming requests — treat it like a password.
Each endpoint receives its own delivery for every event it subscribes to. If an event matches two endpoints, MeetOne makes two separate HTTP requests.
The delivery envelope
Every webhook body is a small JSON envelope with two keys:
{
"event": "room.created",
"payload": { ... }
}
event— the event name, e.g.room.created.payload— the event-specific body. See the event reference for shapes and examples.
Delivery basics
| Property | Value |
|---|---|
| Method | POST |
| Content-Type | application/json |
| User-Agent | meetone_webhook_system/1.0 |
| Timeout | 30 seconds |
Your endpoint should respond within the timeout with a 2xx status code. Any other response — a 4xx, a 5xx, a timeout, or a connection error — is treated as a failure, with different retry behavior depending on the failure type. See Retries and idempotency for details.
Signing secret
Each endpoint has its own signing secret, generated automatically when you create it. MeetOne uses this secret to compute an HMAC-SHA256 signature for every delivery to that endpoint, sent in the X-Webhook-Signature-256 header.
You can rotate the secret at any time from the endpoint's detail page, using the actions menu's Regenerate signing secret option. Any integration still using the old secret will immediately start failing signature verification, so rotate in coordination with your integration.
See Verifying webhook signatures for the exact algorithm and working code examples.
Delivery history
Every delivery attempt is recorded and visible in the admin under Webhook Events, including:
- The payload that was sent
- The HTTP status code your endpoint returned
- The response body your endpoint returned
- The retry count, if the delivery was retried
Use this to debug failing deliveries and to inspect exactly what shape a payload had at the time it was sent.
Next steps
- Webhook events reference — every event type with full example payloads.
- Verifying webhook signatures — how to validate that a delivery really came from MeetOne.
- Retries and idempotency — what happens when your endpoint fails to respond.
- Testing webhooks locally — receiving and verifying deliveries during development.
Questions? Contact us at support@meetone.io.