Umovi integration platform
Build with Umovi
Umovi exposes three deliberately narrow integration surfaces. Use the REST API when your system controls the workflow, webhooks when it needs to react to changes, and MCP when an AI client should discover places or act for a linked Umovi user.
REST API
Resolve services, find slots and manage reservations with a provider-scoped OAuth token.
GET /integrations/v1/providers/{providerId}/slotsGet started Webhooks
Receive signed booking, client and billing events as they happen in Umovi.
X-Umovi-Signature: sha256=<digest>Get started MCP
Let AI clients discover places, check availability and manage bookings with delegated OAuth.
POST https://u-agent.m-cloud.pl/mcpGet started Choose your integration
These surfaces complement each other. A CRM can create reservations through REST and receive later changes through webhooks. An AI assistant can use MCP without receiving access to provider administration APIs.
| Capability | REST API | Webhooks | MCP |
|---|---|---|---|
| Use for | Querying and changing booking data | Reacting to changes in Umovi | AI assistants and agent workflows |
| Communication | Request → response | Umovi → your endpoint | AI client ↔ MCP server |
| Authorization | OAuth2 client credentials | OAuth management + HMAC delivery | Delegated OAuth with PKCE |
| Best for | Voicebots, CRMs and booking automation | Synchronization and notifications | ChatGPT, Claude and MCP clients |
What is intentionally not documented here
Application APIs used by Umovi web and mobile products are not an external integration contract. This portal does not publish /api/v1/auth, client account APIs, provider workspace APIs, brand management, admin operations or internal agent endpoints.
The machine-readable REST contract is available as integration.openapi.json. MCP capabilities are explicitly synchronized from the live server’s tools/list descriptor into a versioned snapshot and published in the tools reference.