Add a LiveKit project to the organisation
consoleSessionvg_session<token>The console's session cookie, set when you sign in. Every operation accepts it, at the role the operation names.
orgId*stringAuthorised orgId; the server must verify organisation/project ownership before any read.
1 <= lengthapplication/json- body
name*stringThe project's display name; trimmed, with at least one letter or digit. Its slug is the project id.
1 <= length <= 64livekitUrl*stringThe LiveKit server URL, with the scheme ws, wss, http or https and a host, such as wss://your-project.livekit.cloud.
1 <= length <= 2048livekitApiKey*stringThe LiveKit API key; unique on this server, since ingest finds a project by the key that signed a webhook or upload.
1 <= length <= 256livekitApiSecret*stringThe LiveKit API secret. Sealed before it is stored; never answered or logged.
1 <= lengthrecordingBucket?An S3 bucket the project keeps its recordings in instead of the instance's bucket. Set only when the project is created; it never changes afterwards, so recordings never move between buckets.
The new project, as getWorkspaces lists it, and how many rooms its LiveKit project had live at the verify. Never its LiveKit key or secret.
application/json- response
id*stringname*stringliveRooms*|Rooms live on the LiveKit project at the verify, from the same signed ListRooms read. Null when the verifier did not count them; never a guessed zero.
0 <= valuecurl -X POST 'https://example.com/api/v1/org/string/projects' \ -H 'Content-Type: application/json' \ -d '{ "name": "string", "livekitUrl": "string", "livekitApiKey": "string", "livekitApiSecret": "string"}'{ "id": "string", "name": "string", "liveRooms": 0}Was this page helpful?