Base URL
https://api.telemio.sh/api/integrations/v1Use a read-scoped MCP workspace credential created inside Telemio’s console, stored in your automation platform’s secret store. Send it as a Bearer token. The endpoint also accepts authorized Telemio user OAuth tokens. Never use an ingest credential for data reads.
Endpoints
| Method | Path | Result |
|---|---|---|
GET | /workspaces | Authorized workspaces only |
GET | /workspaces/{workspaceId}/summary | One-hour telemetry summary |
GET | /workspaces/{workspaceId}/runtimes?limit=50 | Recent runtime sessions, newest first |
Example: list workspaces
curl -fsS \
-H "Authorization: Bearer $TELEMIO_READ_TOKEN" \
https://api.telemio.sh/api/integrations/v1/workspacesExample: summarize one workspace
curl -fsS \
-H "Authorization: Bearer $TELEMIO_READ_TOKEN" \
https://api.telemio.sh/api/integrations/v1/workspaces/WORKSPACE_ID/summaryThe JSON envelope uses a data field, consistent with Telemio’s existing APIs. Authentication failures return HTTP 401 or 403. A workspace outside the credential’s scope returns 404. Runtime polling accepts limits from 1 to 100 and optional status filtering.
OpenAPI contract
Download the OpenAPI 3.1 specification to generate typed clients or inspect request and response schemas.
Next
Use the or to connect this API to a workflow.