Files
Rahul Tarak d17a268d3f docs: sessions-first rewrite — new guides, examples & components (+ core 0.13.0 SDK changes) (#3637)
Integration branch for the next docs release: a **sessions-first
documentation rewrite** — new and rewritten guides, example pages,
interactive components, and docs tooling — plus the supporting SDK
changes that the new docs describe.

The bulk of this PR is docs (~24k lines across ~150 commits); the SDK
changes (~5k lines) back the new guides.

## Documentation (the bulk)

- **Sessions-first restructure** — reorganized navigation and section
structure (incl. the "Sandbox (prev workbench)" section), with
v3-reorganization redirects so old URLs keep resolving.
- **Rewritten core guides** — quickstart, configuring sessions, triggers
(creating + subscribing to events), proxy-execute, toolkits
enable/disable, and common FAQ, rewritten in the house voice.
- **New example pages** — local-sandbox PR reviewer, daily standup bot,
and slack bot, with runnable build-ups.
- **New interactive components & diagrams** — triggers flow animation,
manage-connections visual, connection-refresh visual, and the
terminal-kit components.
- **Docs tooling** — a docs-graph link-graph connectivity checker,
search reprioritization (deprioritize legacy pages), and SDK-reference
regeneration.

## Supporting SDK changes

**`@composio/core` → 0.13.0 (minor)**
- `composio.sessions.create()` as the first-class sessions API
(`composio.create()` kept as an alias).
- **MCP is opt-in:** default `create()` / `use()` return native-tool
sessions (`SessionWithoutMcp`); pass `{ mcp: true }` to surface
`session.mcp`. _Migration: read `session.mcp` only after creating with
`{ mcp: true }`._
- `session.sandbox` is the canonical resolved config;
`session.workbench` kept as a deprecated alias. `sandbox` is the
preferred session-config key (`workbench` still accepted).
- `connectedAccounts.updateAcl()` graduated from experimental (alias
kept).
- `triggers.parse()` (parse + optionally verify an incoming webhook) and
`triggers.setWebhookSubscription()`.

**`@composio/experimental` → minor** — local-workbench helpers moved
onto the `@composio/experimental/workbench` subpath (out of
`@composio/core/experimental`), keeping the ~14 KB embedded Python
helper out of core. Plus the experimental Pi provider.

**`@composio/slim` → minor.**

**Python → 0.17.0** — mirrors the TS surface: `composio.sessions` mount
(`tool_router` deprecated), `triggers.parse()` /
`set_webhook_subscription()`, the `sandbox` config key, and
`connected_accounts.update_acl()`.

## Review response (#3664)

Addressed the `@composio/core` review:
- **Security:** `triggers.parse()` no longer fails open — a
present-but-empty `verifySecret` (e.g. unset `COMPOSIO_WEBHOOK_SECRET`)
now throws instead of silently skipping verification; omitting it stays
an explicit opt-out (both SDKs).
- Removed snake_case leakage from `transformWebhookSubscription` (+ the
index signature that allowed it).
- **Removed** the TS-only `connectedAccounts.link()` toolkit
auto-resolve (shipped with cancellability / orphaned-auth-config bugs
and was effectively undocumented; to be reintroduced properly later).
- Unified Python error types on `ValidationError`; added `mcp=True`
Python tests; fixed runtime-portability + error-type test assertions.
- Polished deprecation messages; fixed the backwards `/experimental`
`@deprecated` note and the `SessionWithMcp` JSDoc.

## Testing

- **TS:** `@composio/core` + `@composio/experimental` typecheck pass;
vitest green for the touched suites.
- **Python:** `test_tool_router.py` + `test_triggers.py` pass (161
tests).

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Kshitij Jhunjhunwala <kj@composio.dev>
Co-authored-by: Malay Vasa <malayvasa@gmail.com>
Co-authored-by: Sarah Simionescu <sarah@composio.dev>
Co-authored-by: Kshitij Jhunjhunwala <113939507+KJ-11@users.noreply.github.com>
2026-06-25 18:27:43 -07:00

198 lines
6.3 KiB
Plaintext

---
title: Organization
description: "Organization management"
---
{/* Auto-generated from OpenAPI spec. Edit the overview at api-overviews/organization.mdx, not this file. */}
The Usage API returns **aggregated counts** of tool calls and sessions. Use it to power billing dashboards, customer-facing analytics, or internal utilization reports. For individual events, use the [Logs API](/reference/api-reference/logs).
There are two query shapes:
- **Summary**: totals across one or more entity types in a time window.
- **Breakdown**: one entity type, grouped by a dimension (tool, user, session, etc.).
Each shape comes in an org-scoped and a project-scoped flavor. The org-scoped endpoints are documented below; the project-scoped usage endpoints (`POST /api/v3.1/project/usage/*`) also appear on the [Projects](/reference/api-reference/projects) reference page.
## Authentication
| Endpoint | Header | Scope |
|---|---|---|
| `POST /api/v3.1/org/usage/summary` | `x-org-api-key` *(or org JWT)* | All projects in your org |
| `POST /api/v3.1/org/usage/{entity_type}` | `x-org-api-key` *(or org JWT)* | All projects in your org |
| `POST /api/v3.1/project/usage/summary` | `x-api-key` *(or cookie)* | Single project |
| `POST /api/v3.1/project/usage/{entity_type}` | `x-api-key` *(or cookie)* | Single project |
The org endpoints accept a `project_id` filter so you can slice by project without rotating keys.
## Entity types
| Entity type | What it counts |
|---|---|
| `tool_calls` | Every tool execution (successful or failed) |
| `sessions` | Sessions created |
## Summary
Totals across entity types for a time window.
```bash
curl -X POST https://backend.composio.dev/api/v3.1/project/usage/summary \
-H "x-api-key: YOUR_PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": 1744848000000,
"to": 1744934400000,
"entity_types": ["tool_calls", "sessions"]
}'
```
Response:
```json
{
"entities": {
"tool_calls": { "unit": "count", "total_quantity": "142", "event_count": 142 },
"sessions": { "unit": "count", "total_quantity": "8", "event_count": 8 }
}
}
```
### Summary parameters
| Field | Type | Default | Notes |
|---|---|---|---|
| `from` | number | 30 days ago | Epoch milliseconds |
| `to` | number | now | Epoch milliseconds |
| `entity_types` | string[] | all | Subset of `tool_calls`, `sessions` |
| `filters.user_id` | string \| string[] | — | Filter events by initiating user |
| `filters.session_id` | string \| string[] | — | Filter events by session |
| `filters.project_id` | string \| string[] | — | Only meaningful on org endpoints; ignored on project endpoints |
## Breakdown
One entity type, grouped by a dimension. Useful for answering "top N" questions.
```bash
curl -X POST https://backend.composio.dev/api/v3.1/project/usage/tool_calls \
-H "x-api-key: YOUR_PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"from": 1744848000000,
"to": 1744934400000,
"group_by": "toolkit_slug",
"order_by": "total_quantity",
"order_direction": "desc",
"limit": 10
}'
```
Response:
```json
{
"entity_type": "tool_calls",
"unit": "count",
"total_quantity": "142",
"event_count": 142,
"groups": [
{ "key": "github", "total_quantity": "80", "event_count": 80 },
{ "key": "slack", "total_quantity": "62", "event_count": 62 }
]
}
```
### Breakdown `group_by` options
| Entity | Org scope | Project scope | Default |
|---|---|---|---|
| `tool_calls` | `tool_slug`, `toolkit_slug`, `connected_account_id`, `user_id`, `session_id`, `project_id` | same minus `project_id` | `tool_slug` |
| `sessions` | `user_id`, `project_id` | `user_id` | `user_id` |
### Breakdown parameters
| Field | Type | Default | Notes |
|---|---|---|---|
| `from` | number | 30 days ago | Epoch ms |
| `to` | number | now | Epoch ms |
| `group_by` | string | see table | Dimension to group by |
| `order_by` | string | `total_quantity` | One of `key`, `total_quantity`, `event_count` |
| `order_direction` | `"asc"` \| `"desc"` | `"desc"` | |
| `limit` | number | 50 | Max groups returned |
| `filters` | object | — | See Filters below |
## Filters
Filters live in a `filters` object on the request body. Each filter value can be a **single string** or an **array of strings**:
- Within a single field, values are OR-combined (`user_id: ["a", "b"]` matches events for user *a or b*).
- Across fields, filters are AND-combined.
```json
{
"filters": {
"user_id": ["user_123", "user_456"],
"session_id": "sess_abc"
}
}
```
The `project_id` filter is only meaningful on the org-scoped endpoints. Project endpoints accept the field but ignore it (your key already pins the scope to a single project).
## Time ranges
- `from` and `to` are **epoch milliseconds**.
- `from` defaults to 30 days before `to`.
- `to` defaults to the current time.
- Maximum range: **366 days**. Longer ranges return a 400.
## Recipes
### Top 10 tools my org called last week
```bash
WEEK_AGO=$(( $(date +%s) - 604800 ))000
NOW=$(date +%s)000
curl -X POST https://backend.composio.dev/api/v3.1/org/usage/tool_calls \
-H "x-org-api-key: YOUR_ORG_API_KEY" \
-H "Content-Type: application/json" \
-d "{
\"from\": ${WEEK_AGO},
\"to\": ${NOW},
\"group_by\": \"tool_slug\",
\"limit\": 10
}"
```
### Tool call count per user for my project this month
```bash
MONTH_AGO=$(( $(date +%s) - 2592000 ))000
NOW=$(date +%s)000
curl -X POST https://backend.composio.dev/api/v3.1/project/usage/tool_calls \
-H "x-api-key: YOUR_PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d "{
\"from\": ${MONTH_AGO},
\"to\": ${NOW},
\"group_by\": \"user_id\",
\"limit\": 50
}"
```
### Which toolkits is a specific user using?
```bash
curl -X POST https://backend.composio.dev/api/v3.1/project/usage/tool_calls \
-H "x-api-key: YOUR_PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"group_by": "toolkit_slug",
"filters": { "user_id": "user_abc123" }
}'
```
## Endpoints
<ApiEndpointsTable endpoints={[{"method":"POST","pathV31":"/api/v3.1/org/usage/summary","pathV3":"/api/v3/org/usage/summary","summary":"Org usage summary","href":"/reference/api-reference/organization/postOrgUsageSummary"},{"method":"POST","pathV31":"/api/v3.1/org/usage/{entity_type}","pathV3":"/api/v3/org/usage/{entity_type}","summary":"Org usage breakdown","href":"/reference/api-reference/organization/postOrgUsageByEntityType"}]} />