Services, people and search
Read services and the people who provide them. You can also match a service mentioned in a conversation to a catalogue entry.
catalog · search · resolveIntegration API
Bookings in your system. The calendar stays in Umovi.
Read services, check available times and manage bookings from your own system. OAuth2 access covers one organisation’s data.
Server-to-server REST API · OAuth2 client credentials · signed webhooks
A real API transaction
POST /reservations
201 CreatedRequest
{
"serviceId":
"2c4f3d1e-0e4a-4f9f-91cf-00c59a652f4a",
"employeeId":
"86c8a0ab-e419-4a13-bc8f-13112c9a2a45",
"startAt": "2026-09-03T17:30:00+02:00",
"client": { "phone": "+48…" },
"source": "partner-crm"
}Response
Reservation created
bookingId · confirmed · 17:30
Source saved
partner-crm · crm-1842
What you can connect
From choosing a service to changing a booking.
Choose the operations your integration needs. Continue managing services, schedules and rules in your Umovi workspace.
Availability
Search a date range or ask for the first slot that matches the selected service and employee.
slots · first availableClients and reservations
Find or create a client, then create, inspect, update, reschedule or cancel the reservation.
clients · reservations · historyWebhooks
Subscribe to booking events, inspect deliveries, send a test and rotate the signing secret.
signed delivery · test · rotationAfter the request
Your system stays up to date.
A signed webhook can notify the integration when the booking changes. Delivery history makes retries and operational checks visible.
Signed booking events
booking.createdbooking.updatedbooking.cancelledSigning secret available at subscription creation
Delivery history for each subscription
Built-in test delivery and secret rotation
API documentation and tester
Start in the docs, test every operation in the browser.
The documentation includes the OpenAPI contract and an API tester that sends requests directly to the selected Umovi API origin.
Other ways to connect