REST Integration API · Umovi Integrations

The Integration API is a server-to-server REST surface under /integrations. It uses OAuth2 client credentials and never relies on an Umovi user session.

Base URL:       https://u-api.m-cloud.pl
Token endpoint: POST /integrations/oauth/token
Resources:      /integrations/v1/providers/{providerId}/*
OpenAPI:        /integrations/openapi.json

What it can do

Area	Capabilities
Catalog	Read the booking catalog, search services and employees, resolve spoken names into valid pairs.
Clients	Recognize callers by exact phone number; search, create, update and delete provider client records.
Slots	Search date and time windows; find the earliest or latest slot within a bounded search.
Reservations	Create, list, read, update, reschedule and cancel reservations; read lifecycle history.
Webhooks	Create integration-owned subscriptions, inspect deliveries, send a test and rotate the signing secret.

First request

Create an integration client in the provider workspace and store its secret immediately—it is shown once. Then obtain a token:

curl https://u-api.m-cloud.pl/integrations/oauth/token \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": "'$CLIENT_ID'",
    "client_secret": "'$CLIENT_SECRET'",
    "grant_type": "client_credentials"
  }'

Use the returned access_token:

curl 'https://u-api.m-cloud.pl/integrations/v1/providers/'$PROVIDER_ID'/catalog' \
  -H 'Authorization: Bearer '$ACCESS_TOKEN

The token and every resource are provider-scoped. A client issued for one provider cannot read or change another provider's data, even if a different providerId is supplied in the path.

Test without installing a client

The Integration API tester covers every operation from the current integration OpenAPI document. Requests go directly from your browser to the selected API origin; the documentation server does not proxy or store credentials.