List Connected Apps
Apps connected to this workspace through OAuth (MCP connectors), newest first: your own, or everyone's for admins.
API key access
/api/v1/workspaces/current/connected-appsAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/workspaces/current/connected-apps" \ -H "X-Workspace-Id: string"{
"items": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"client_id": "string",
"client_name": "string",
"client_uri": "string",
"user_id": "a169451c-8525-4352-b8ca-070dd449a1a5",
"user_email": "string",
"scopes": [
"string"
],
"created_at": "2019-08-24T14:15:22Z",
"last_used_at": "2019-08-24T14:15:22Z"
}
]
}Get Consent Request
What a signed authorization request asks for: the app, where the browser returns, the scopes, and the signed-in user's workspaces. 400 `invalid_request` for a bad or expired request.
Protected Resource Metadata (MCP)
The same document at the path-suffixed location (RFC 9728 §3.1) that a 401 from `/api/v1/mcp` names in `WWW-Authenticate: Bearer resource_metadata=...`.