Workspaces

The rest of the API assumes you already know the workspace ID. That holds for an API Key: whoever minted it knew. An MCP client connected through OAuth does not: the user picked workspaces on the consent screen and the model has never seen those IDs.

This endpoint is that directory. The MCP tool list_workspaces is the same call.

GET https://api.platica.mx/v1/workspaces

It is not gated on a workspace module: knowing which teams you belong to is not something a role hides, and an OAuth client needs this list before it can name a workspace on any other route.

It accepts both Bearer credentials: an OAuth access token (pl_at_…) or an API Key (pl_key_…). See Authentication .

Response

{
  "active": null,
  "requires_workspace_argument": true,
  "credential": {
    "type": "oauth",
    "scopes": ["platica:read", "platica:write", "offline_access"]
  },
  "count": 2,
  "workspaces": [
    {
      "id": "g6yCA16pkWl5eXo7KszB",
      "name": "Acme Norte",
      "role": "admin",
      "modules": "all"
    },
    {
      "id": "k2pL90vQmN4sHxYwR8cD",
      "name": "Acme Support",
      "role": "operator",
      "modules": ["dashboard", "conversations", "agents", "campaigns", "contacts", "chat"]
    }
  ]
}

Errors