> ## Documentation Index > Fetch the complete documentation index at: https://docs.phoneuse.com/llms.txt > Use this file to discover all available pages before exploring further. # Where the media server delivers room events > NOT AN ENDPOINT YOU CALL. The media server behind live video posts here when somebody joins or leaves a device's room and when a stream's tracks come and go. What it drives is one thing: a robot arm's live stream stops a few seconds after its last viewer leaves, instead of the 30 seconds the arm waits by itself. It changes nothing a customer holds. NO CREDENTIAL OF OURS AUTHENTICATES IT, because the sender holds none. A delivery is authenticated by a token in `Authorization`, signed with the media server project's secret and carrying the SHA-256 of the body, checked before the body is parsed. WHAT THE STATUS CODES MEAN. 200 is settled, including a repeat of an event already handled and an event this service does not read. 400 is an authentic delivery that is not readable as an event. 401 is a delivery that is not authentic. A repeat of an event id already handled changes nothing. A body over 65536 bytes is refused as it streams. ON A DEPLOYMENT WITHOUT LIVE VIDEO CONFIGURED it answers 404, as if it were not there. Hosted deployments only. A local checkout does not mount this route, so calling it there is a 404. ## OpenAPI ````yaml /api/openapi.json post /webhooks/livekit openapi: 3.1.0 info: title: Phonebase HTTP API version: 0.1.0 summary: >- Every HTTP operation the control plane mounts, generated from the app's own route table. description: >- The control plane exposes two HTTP surfaces, and reading the boundary between them matters more than reading any single endpoint. The CONTROL surface is what your backend and your operators call. It takes a bearer token in the `Authorization` header, and two credential channels resolve to the same authorization context: an OAuth 2.1 access token for interactive clients, or an org scoped API key for headless ones. The DEVICE surface, under `/vrx/{runToken}/v1`, is what a worker calls while executing one run. Its credential is the run token in the url path, and it reads no `Authorization` header at all. Device control itself is not REST. An agent taps, swipes and reads the screen over the Model Context Protocol at `POST /mcp`, one tool call at a time. There is no `POST /v1/devices/{id}/tap`, and if you are looking for one, start with the tool reference instead. Operations marked `"x-phonebase-modes": ["hosted"]` exist only on a hosted deployment; a local checkout does not mount them. servers: - url: '{origin}' description: Your control plane origin. variables: origin: default: https://mcp.phonebase.co enum: - https://mcp.phonebase.co - http://127.0.0.1:8788 description: >- The hosted deployment serves the public origin its metadata document advertises, and that is the default here. Select the loopback entry instead when you are running a local checkout, which serves the port `PORT` names. security: [] tags: - name: Apps description: Save immutable application builds and manage explicit device operations. - name: Managed Proxy description: >- Organization-owned fixed egress resources, independent one-time orders and verified network relationships. - name: Health description: Liveness, unauthenticated. - name: Gateway enrollment description: >- How a new gateway computer trades a one-time enrollment code for its tunnel credential. Unauthenticated: the code is the credential. - name: Gateway releases description: >- What a gateway computer installs: the current edge release of a channel. Called with the gateway's own credential. - name: MCP description: The JSON-RPC endpoint an agent drives devices through. - name: Copilot description: >- Drive a device by chatting. A signed in person's own conversations, streamed. Hosted deployments only. - name: Discovery description: Where to authenticate. Served on hosted deployments only. - name: Runs description: Start, watch and steer a run. - name: API keys description: Mint and revoke headless credentials. Hosted deployments only. - name: Device surface description: What a worker calls with its run token to observe and act. - name: Usage description: Read your org's own receipts and consumption. Hosted deployments only. - name: Devices description: Read the fleet your credential can see. Hosted deployments only. - name: Notifications description: >- What a person needs to know when they are not watching, and which emails they receive. Hosted deployments only. - name: Webhooks description: >- Subscribe your own system to what happens here, and read what was delivered. Hosted deployments only. - name: Provisioning description: >- Whether an organisation is provisioned, and how it becomes so. Hosted deployments only, and both operations answer a declared 503 on a deployment that cannot provision yet. paths: /webhooks/livekit: post: tags: - Devices summary: Where the media server delivers room events description: >- NOT AN ENDPOINT YOU CALL. The media server behind live video posts here when somebody joins or leaves a device's room and when a stream's tracks come and go. What it drives is one thing: a robot arm's live stream stops a few seconds after its last viewer leaves, instead of the 30 seconds the arm waits by itself. It changes nothing a customer holds. NO CREDENTIAL OF OURS AUTHENTICATES IT, because the sender holds none. A delivery is authenticated by a token in `Authorization`, signed with the media server project's secret and carrying the SHA-256 of the body, checked before the body is parsed. WHAT THE STATUS CODES MEAN. 200 is settled, including a repeat of an event already handled and an event this service does not read. 400 is an authentic delivery that is not readable as an event. 401 is a delivery that is not authentic. A repeat of an event id already handled changes nothing. A body over 65536 bytes is refused as it streams. ON A DEPLOYMENT WITHOUT LIVE VIDEO CONFIGURED it answers 404, as if it were not there. Hosted deployments only. A local checkout does not mount this route, so calling it there is a 404. operationId: postWebhooksLivekit requestBody: description: >- The media server's own event envelope, byte for byte as it sent it. Read only once the signature matches. required: true content: application/json: schema: type: object properties: id: type: string description: >- The media server's id for this event. What makes a repeat recognisable. event: type: string description: >- The event type. `room_started`, `room_finished`, `participant_joined`, `participant_left`, `track_published` and `track_unpublished` are read; any other is settled and ignored. room: type: object additionalProperties: true description: The room, by `name`. participant: type: object additionalProperties: true description: Who joined or left, by `sid` and `identity`. track: type: object additionalProperties: true description: Which track, by `sid`. required: - id - event additionalProperties: true description: >- The media server defines this shape. Fields beyond the ones named here travel through and are ignored. responses: '200': description: >- Settled. `outcome` names what was done: `published`, `ignored` or `duplicate`. content: application/json: schema: type: object properties: received: type: boolean const: true description: Always true on this response. outcome: type: string enum: - published - ignored - duplicate description: >- What was done with the event. Not a field to branch on: the sender does not read it. required: - received - outcome additionalProperties: false '400': description: >- `invalid_event`: authentic, but not readable as an event (no `id` or no `event`). Nothing was done. content: application/json: schema: type: object properties: error: type: object properties: code: type: string const: invalid_event description: Always `invalid_event`. required: - code additionalProperties: false required: - error additionalProperties: false '401': description: >- `invalid_signature`: no token, a token this project did not sign, an expired one, or one whose body hash does not match. Nothing was read off the body. Why is kept out of the answer on purpose. content: application/json: schema: type: object properties: error: type: object properties: code: type: string const: invalid_signature description: Always `invalid_signature`. required: - code additionalProperties: false required: - error additionalProperties: false '404': description: This deployment has no live video configured. '413': description: >- The request body exceeds the server's limit (1 MiB). Refused before the body is parsed, so nothing was partially applied. Retrying the same body will fail the same way: send less. Per-field limits are tighter than this and are documented on the fields themselves; this is the backstop underneath them. The shape is the same on ordinary JSON surfaces, /vrx included. The explicitly configured APK content stream documents its own byte ceiling. content: application/json: schema: $ref: '#/components/schemas/PayloadTooLargeError' '429': description: >- Over the request budget for this caller. Hosted deployments only. Which budget applied depends on whether this request carried an `Authorization` header, not on which endpoint it was aimed at. Wait `Retry-After` seconds and retry the same request: the refusal happens before any work, so nothing was partially applied. See /api/rate-limits. headers: Retry-After: description: >- Whole seconds until one request is available again. Computed from the caller's own remaining allowance, not a fixed constant. schema: type: string RateLimit-Limit: description: >- The budget in effect for this caller class, in requests per minute. schema: type: string RateLimit-Remaining: description: >- Whole requests that were still available when this request was admitted. Zero on a 429. schema: type: string RateLimit-Reset: description: >- Seconds until the allowance is back to full. Longer than `Retry-After`, which is the wait for a single request. schema: type: string RateLimit-Policy: description: The budget and its window, as `;w=60`. schema: type: string content: application/json: schema: $ref: '#/components/schemas/RateLimitedError' security: [] components: schemas: PayloadTooLargeError: type: object properties: error: type: object properties: code: type: string const: payload_too_large description: Always `payload_too_large` on this response. message: type: string description: A human readable summary naming the limit in bytes. required: - code - message additionalProperties: false required: - error additionalProperties: false description: >- Returned when the request body exceeds the server limit. Identical on every surface, including /vrx. RateLimitedError: type: object properties: error: type: object properties: code: type: string const: rate_limited description: Always `rate_limited` on this response. message: type: string description: >- A human readable summary. The numbers are in the headers, not in here. required: - code - message additionalProperties: false required: - error additionalProperties: false description: >- Over the request budget. Raised by the rate limiter before any handler runs, which is why its code is not one of the action codes: nothing was attempted, so no action failed. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.