Skip to content

Meet

Video meetings and rooms.

Open Meet
Checked against the dashboard on November 19, 2026

Meet has one public method of its own. Rooms, meetings, recordings, messages, calls and the plan are managed in the dashboard, and the Meet screens are the only way in to them. A second public method, which belongs to Calendar, makes the Meet room of a video booking.

A public meeting link ends in a room name of three letters, four letters and three letters joined by hyphens, like abc-defg-hij. resolve_meet_slug turns that name into the room behind it. It is public, so it needs no API key.

curl -s https://xuda.ai/cpi/resolve_meet_slug \
  -H 'content-type: application/json' \
  -d '{"slug":"abc-defg-hij"}'
const res = await fetch('https://xuda.ai/cpi/resolve_meet_slug', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({ slug: 'abc-defg-hij' }),
});
const { code, data } = await res.json();
import requests

res = requests.post(
    'https://xuda.ai/cpi/resolve_meet_slug',
    json={'slug': 'abc-defg-hij'},
)

A good answer has code 1, and data holds the room:

json
{
  "code": 1,
  "data": {
    "slug": "abc-defg-hij",
    "room_id": "ROOM_ID",
    "owner_uid": "OWNER_ACCOUNT_ID",
    "region": "REGION"
  }
}

A link that never existed and a link that was revoked, which is what deleting a room does, give the same answer on purpose: code is -61 and data says unknown meeting link. A name that is not three, four and three letters gets that answer too. The answer never says which of the two it was, so the method cannot be used to find out which links used to be real.

Make the room of a video booking

A booking taken through a Calendar service whose meeting is Video gets a Meet room when it is confirmed. create_booking_room makes the room for a confirmed video booking that has none, and sends each guest of that appointment the link. It acts for the account whose API key you use.

curl -s https://xuda.ai/cpi/create_booking_room \
  -H 'content-type: application/json' \
  -d '{"api_key":"YOUR_API_KEY","uid":"YOUR_ACCOUNT_UID","booking_id":"BOOKING_ID"}'
const res = await fetch('https://xuda.ai/cpi/create_booking_room', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    api_key: 'YOUR_API_KEY',
    uid: 'YOUR_ACCOUNT_UID',
    booking_id: 'BOOKING_ID',
  }),
});
const { code, data } = await res.json();
import requests

res = requests.post(
    'https://xuda.ai/cpi/create_booking_room',
    json={
        'api_key': 'YOUR_API_KEY',
        'uid': 'YOUR_ACCOUNT_UID',
        'booking_id': 'BOOKING_ID',
    },
)

A good answer has code 1 and data holds join_url and slug. The room belongs to the appointment, so every confirmed booking of it holds the same room. Calling it twice is safe: the second call answers the room that exists and sends nothing again.

It is refused, with a message, for a booking that is cancelled, one that already happened, one that is not a video appointment, and one that is not yours. It is also refused when no profile can be found to make the room under. To act on the calendar of an account that shared it with you at the edit level, pass its share_id.

How is this guide?

Last updated on November 15, 2026