Webhooks overview

Webhooks deliver changes from Umovi to your HTTPS endpoint. They are useful for CRM synchronization, automation, call-center screens and follow-up workflows.

Create a subscription

Use an Integration API token with webhooks:write:

POST /integrations/v1/providers/{providerId}/webhooks
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "url": "https://example.com/umovi/webhooks",
  "events": [
    "booking.created",
    "booking.rescheduled",
    "booking.cancelled_by_client"
  ],
  "isActive": true
}

The response contains a plain-text signing secret exactly once. Store it before discarding the response.

Ownership

A webhook created through the Integration API is bound to the authenticated OAuth client. That client can list, update, test, rotate or delete only its own webhooks for its provider.

Endpoint requirements

• Use a publicly reachable HTTPS endpoint. Production target policy blocks private/loopback addresses by default; exceptions depend on explicit environment policy.
• Use the final endpoint URL: redirects are not followed and 3xx responses count as failures.
• Accept POST with Content-Type: application/json.
• Read the raw request body before parsing JSON; the raw bytes are part of the signature.
• Verify signature and timestamp before processing.
• Return any 2xx response within 15 seconds.
• Queue durable work and acknowledge quickly instead of performing long processing inline.