API and webhooks
Add bookings to your system
For CRMs, internal systems, partner applications and booking automations that need services, availability, clients and reservations.
OAuth2 · REST · signed webhooks
Umovi integrations
One calendar. Bookings from different places.
Clients can choose a time on the website, in the app or through a connected assistant. Your system and a partner’s voicebot can also check availability in Umovi. You see the bookings in the same calendar.
Clientweb / app
SystemREST
AI agentMCP
VoicebotAPI
Availability
Services · people · rules
What would you like to connect?
Choose how to connect to Umovi.
Explore the API
AI agents and MCP
Let an agent complete the booking
An assistant that supports MCP can find a place, check availability and help a client book a time.
21 tools · delegated OAuth · MCP Apps
Voicebots
Turn a call into a booked appointment
A telephony or voicebot partner uses the Integration API to resolve a service, check a real slot and create the reservation in Umovi.
Partner solution · Integration API
One booking record
See the booking and where it came from.
Booking details show where a booking came from and what has changed. You don’t have to look across several tools.
The same booking rules
Service durations, working hours and breaks determine which times can be booked, including through an integration.
A visible source
The booking history identifies the client surface, MCP app or integration that created it.
Manage bookings in one calendar
Confirm, reschedule or complete a booking in Umovi, wherever it came from.
Booking details
Alex Morgan
- Service
- Cut & style
- Time
- 10:00–10:45
- Specialist
- Marta
History and source
Booking events, channel and changes.
Booking created
Client · Umovi web
Status: pending confirmation
Automatically confirmed
System · automation
Pending → confirmed
The shared foundation
The same times and rules across every connection.
Umovi checks availability, conflicts and required consent. Each integration can access only the features and data covered by its permissions.
Provider boundaries
API credentials and resources are limited to the provider they belong to.
Consent before booking
MCP does not guess consent. When it is required, the agent must ask the user explicitly.
Safe retries
Idempotency prevents a repeated integration request from creating the same appointment twice.
Not sure where to start?
Tell us which tools you use.
We will help choose between MCP, the Integration API and a partner voicebot connection.