# Plix API > Read an organization's cameras, people, locations, events and recordings, and start and stop livestreams, shifts and recordings on its cameras. People can also connect an AI assistant to Plix; see the connector guide. Base URL for API calls: https://beaver.plix.ai ## Reference - [OpenAPI description](/v1/openapi.json): every endpoint, parameter, response and error, as JSON - [Reference page](/docs): the same description, rendered for people - [Docs overview](/docs.md): what Plix offers and where each reference is, as Markdown - [Connector guide](/docs/connector.md): how to connect an AI assistant to Plix (MCP), as Markdown ## Getting started The API base URL is `https://beaver.plix.ai`. Plix issues credentials for your organization. Send request bodies as JSON with `Content-Type: application/json`; responses are JSON. Exchange your client id and secret for an access token: ```sh curl --request POST 'https://dev-q4b765oq5ggoon2l.us.auth0.com/oauth/token' \ --header 'Content-Type: application/json' \ --data '{"client_id":"YOUR_CLIENT_ID","client_secret":"YOUR_CLIENT_SECRET","audience":"https://beaver.plix.ai","grant_type":"client_credentials"}' ``` Use the returned `access_token` to list your cameras: ```sh curl 'https://beaver.plix.ai/v1/devices' \ --header 'Authorization: Bearer ' ``` ## Authentication Use Auth0 client credentials: POST to the token URL above with `grant_type: client_credentials` and `audience: https://beaver.plix.ai`. Send the access token as `Authorization: Bearer ` on every API call. Keep the client secret private and obtain another token when the current one expires. A credential belongs to one organization and can access only that organization's data. Missing or invalid tokens return `401` with `error: invalid_token`. Token-verification failures, including an unavailable signing-key service, also return 401. Malformed credentials can return `400 invalid_request`. ## Permissions Each operation lists its required permission in `x-plix-scopes`. A credential without that permission receives `403 insufficient_scope`. Ask Plix to grant the permissions your integration needs. Some older credentials hold `read:soc`. It covers `read:devices`, `read:personnel`, `read:assignments`, `read:locations` and `read:events`. It does not grant signal-strength, recording, or control permissions. ## Support Email support@plix.ai. ## Connect an assistant The Plix connector lets a person's AI assistant read what that person sees in Plix: Coaching results, the recordings they can open, and what was said in those recordings. It is a remote MCP server. Every tool only reads; nothing in Plix can be changed through it. MCP endpoint: `https://beaver.plix.ai/mcp` (streamable HTTP). Sign-in is OAuth in a browser, with the person's Plix login; there is no API key. Tools (all read-only): - `coaching_overview`: Coaching overview - `coaching_procedure`: Coaching procedure - `coaching_evidence`: Coaching clips - `recordings_list`: Recordings - `recording_transcript`: Recording transcript Who can use it, setup steps for each assistant, limits and troubleshooting: [connector guide](/docs/connector.md) ## Endpoints - `POST /v1/livestream/start`: Start a livestream. Permission: `livestream:control`. - `POST /v1/livestream/keepalive`: Keep a livestream running. Permission: `livestream:control`. - `POST /v1/livestream/stop`: Stop a livestream. Permission: `livestream:control`. - `POST /v1/shift/start`: Start a shift on a camera. Permission: `shift:control`. - `POST /v1/shift/stop`: Stop a shift on a camera. Permission: `shift:control`. - `POST /v1/recording/start`: Start a recording on a camera. Permission: `recording:control`. - `POST /v1/recording/stop`: Stop a recording on a camera. Permission: `recording:control`. - `GET /v1/recordings`: List recordings. Permission: `read:orgVideos`. - `GET /v1/devices`: List devices. Permission: `read:devices`. - `GET /v1/personnel`: List personnel. Permission: `read:personnel`. - `GET /v1/locations`: List the latest location of each device. Permission: `read:locations`. - `GET /v1/locations/{deviceId}/history`: Get the location history of a device. Permission: `read:locations`. - `GET /v1/signal-strength`: List the latest signal strength of each device. Permission: `read:telemetry`. - `GET /v1/signal-strength/{deviceId}/history`: Get the signal strength history of a device. Permission: `read:telemetry`. - `GET /v1/events`: List events. Permission: `read:events`. - `GET /v1/assignments`: List device assignments. Permission: `read:assignments`.