API and webhooks

Umovi bookings in your own system

Let clients choose a service and available time in your portal, CRM or app. Use the API to save the booking in Umovi and webhooks to receive updates when it changes.

See how it worksAPI documentation

Example: your client portal

How a portal booking reaches Umovi

Follow a client portal example through checking availability, saving a booking and receiving an update after a time change.

  1. 01

    Your portal shows available times.

    Your portalUmovi availability

    It reads services, staff and free times from Umovi. The client chooses a time that respects the working hours, service duration and breaks in the calendar.

  2. 02

    The booking reaches your team.

    Client selectionTeam calendar

    Your portal sends the chosen time and client details. Umovi checks availability when saving. Once created, the booking appears in the calendar and your portal receives its ID.

  3. 03

    Changes return to your portal.

    Change in UmoviPortal update

    A team member reschedules the booking in Umovi. A webhook notifies your system, which can fetch the current details and show the client the new time.

When it helps

Where you can use the Umovi API

Your own portal or app

Clients choose a time where they already order a service or manage their account.

CRM and client support

An adviser checks availability and books a time in the tool they use for the conversation.

Automation after a booking

A new, rescheduled or cancelled booking triggers the next step in your system.

Just want to let clients book online? Start with your Umovi profile and a booking link.

Explore the business workspace

Implementation scope

What you need to build the integration

Your system needs development work to support the integration. A developer builds the form, data mapping and update handling. In Umovi, you set up services, availability and access permissions.

In Umovi

Set up services, your team, working hours and integration access for your business.

In your system

Your developer links client and booking records, handles unavailable times and processes updates from Umovi.

For the developer

How to connect to the API

Server-to-server REST, OAuth2 client credentials and access scoped to one business. Keep the integration secret on your server.

Operations and conditions to handle
  1. 01

    Get a token and the catalogue.

    Create an integration client in the business workspace, save the secret shown once and request a token. The catalogue provides services and staff for choosing a time.

  2. 02

    Check availability before saving.

    Handle availability conflicts. Use Idempotency-Key for retries and pass your own record ID as externalReservationId.

  3. 03

    Receive updates over HTTPS.

    Verify the HMAC signature against the raw body. Webhooks can arrive more than once and out of order: deduplicate deliveries and fetch the current booking state.

REST · /integrations

POST /integrations/oauth/token

grant_type: client_credentials

/integrations/v1/providers/{providerId}
  GET  /catalog
  POST /reservations
  POST /webhooks

Idempotency-Key: <unique-request-key>

booking.created
booking.rescheduled
booking.cancelled_by_client
Open the REST documentationLaunch the API tester

Have a workflow to connect?

Tell us about your system

Tell us which system you use and what should happen after a time is chosen. We will work out the scope of the Umovi integration.

Discuss your integrationShare the docs with your developer