---
title: "Start Call"
method: POST
path: "/api/me/conversations/{conversation_id}/call"
---

# Start Call

`POST /api/me/conversations/{conversation_id}/call`

## Request

- Base URL: `https://api.meet-align.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.meet-align.com/api/me/conversations/{conversation_id}/call`
- Auth: none declared

"Start a call" from a DM's video icon — a real, standalone 1:1
video call: a bare LiveKit room (execution/direct_calls.py +
execution/voice.py's `create_room`/`mint_token`), no Align Room /
RoomManager involved anywhere — no phases, no AI review, no quota,
no join-ceremony tab, just a token for VideoCallDialog.tsx to
connect with directly. (Used to mint a full `kind="meet"` Rooms
room here; that meant every plain call dragged Align's whole
review-session machinery behind it for no reason — see
direct_calls.py's docstring.) Scoped to DMs — "call the person I'm
talking to", not a group conference; a channel gets a clear 400
rather than silently ringing nobody in particular.

The callee's live presence never blocks this: the call is minted
either way, and `calleeOnline` just decides the caller's toast
("ringing" vs. "share the link") — chat_sio.notify_incoming_call is
a no-op emit to an empty room if they're offline.

## Path parameters

- `conversation_id` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/meet-align/apis/hudl-api.md) · [All operations](https://skmtc.dev/meet-align/apis/hudl-api/llms.txt) · [OpenAPI document](https://skmtc.dev/meet-align/apis/hudl-api/revisions/3f4c53c5b564?raw)