---
canonical_url: "https://docs.composio.dev/docs/security/audit-logs"
markdown_url: "https://docs.composio.dev/docs/security/audit-logs.md"
product: "platform"
version: null
last_updated: null
---

# Audit logs (/docs/security/audit-logs)

Audit logs show who changed your organization and when. Composio records an event each time someone changes your organization or its members, projects, API keys, webhook subscriptions, or session configs. It records changes made in the dashboard, through the API, and with the CLI.

Use audit logs to find out who revoked an API key, who turned off two-factor authentication for a project, or what a member changed before they left your team.

> Only organization admins can view audit logs.

## View audit logs [#view-audit-logs]

1. In the dashboard, open [**Organization Settings > Audit logs**](https://dashboard.composio.dev/~/org/settings/audit-logs?utm_source=docs\&utm_medium=content\&utm_campaign=docs-audit-logs).
2. Choose a time range. The page opens on the last 7 days, with the newest events first.
3. To narrow the list, filter by member or by event.

For example, filter by one member to see everything they changed. Filter by **Member removed** to see who removed people from your organization.

## What each event shows [#what-each-event-shows]

| Column     | What it shows                                                                                                           |
| ---------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Time**   | When the change happened.                                                                                               |
| **Member** | The current email of the member who made the change. A change made with an API key shows the member the key belongs to. |
| **Event**  | What changed, in one sentence, such as "Revoked API key ci-deploy" or "Renamed project to support-bot".                 |
| **IP**     | The IP address the request came from, when Composio has one.                                                            |
| **Source** | How the change was made, such as **Dashboard**, **Project API key**, **Org API key**, **User API key**, or **CLI**.     |

Changes that Composio makes, such as a plan change by Composio support, show **Composio** as the member and no IP address. If a member's account was deleted, their events show **Deleted member**. When someone reports a leaked API key through the [key revocation endpoint](/reference/api-reference/api-keys/postApiKeyRevocation), Composio revokes the key, and the event shows **Leaked key report** as the member and the source.

When one change revokes several keys, the log shows a single summary event next to it. For example, removing a member who owns three project API keys records the removal and a second event, "Revoked 3 API keys".

## What audit logs record [#what-audit-logs-record]

| Area                  | Recorded changes                                                                                                                                                                    |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Organization          | Creating, renaming, deleting, or restoring the organization, and plan changes made by Composio support                                                                              |
| Members and invites   | Creating or revoking an invite, a member joining, changing a member's role, and removing a member                                                                                   |
| Projects              | Creating, renaming, or deleting a project, and changing its settings, such as two-factor authentication, Zero Data Retention, Instant, or triggers                                  |
| API keys              | Creating or revoking project API keys and changing their allowed IPs. Regenerating or revoking organization API keys. Creating or revoking user API keys, and approving a CLI login |
| Webhook subscriptions | Creating, updating, or deleting a subscription, and rotating its secret                                                                                                             |
| Session configs       | Creating, updating, archiving, or restoring a session config                                                                                                                        |

## What audit logs don't record [#what-audit-logs-dont-record]

Audit logs cover changes to how your organization is set up, so they don't record the following.

* Tool calls, sessions, and trigger events. These appear in your project's logs, which you can also [stream to a SIEM](/docs/poc-to-prod/stream-logs-to-a-siem).
* Changes to connected accounts, auth configs, and triggers.
* Sign-ins, and requests that fail or change nothing.
* Plan changes you make in **Organization Settings > Billing**.

## How far back audit logs go [#how-far-back-audit-logs-go]

On the Hobby plan, audit logs cover the last 30 days. On paid plans, they cover the last 12 months.

---

📚 **More documentation:** [View all docs](https://docs.composio.dev/llms.txt) | [Changelog](https://docs.composio.dev/docs/changelog.md) | [Glossary](https://docs.composio.dev/llms.mdx/reference/glossary) | [Examples](https://docs.composio.dev/llms.mdx/examples) | [API Reference](https://docs.composio.dev/llms.mdx/reference)

---

# Composio SDK — Notes for AI Code Generators

**Purpose:** Reference for generating current (v3) [Composio](https://composio.dev/) integration code.
**Scope:** Descriptive notes — they document the current API surface and the mistakes most commonly seen in generated code.

---

## 1. Recommended Integration: Sessions

For agent tool delivery, Composio supports **Native Tools** (with a provider package) and **MCP** (no provider package needed).

For application-owned tools or deterministic backend code, use [managed authentication with Proxy Execute](/docs/authentication/managed-auth-for-custom-tools). A session can provide a user-scoped runtime context without an LLM or MCP. Composio authenticates provider requests server-side; connected-account reads redact credentials and aren't a supported token-export workflow.

### Native Tools

#### Python

```python
# ✅ CORRECT — Python (defaults to OpenAI)
from composio import Composio

composio = Composio()
session = composio.create(user_id="user_123")
tools = session.tools()
# Pass tools to your agent/LLM framework
```

#### TypeScript

```typescript
// ✅ CORRECT — TypeScript (defaults to OpenAI)
import { Composio } from "@composio/core";

const composio = new Composio();
const session = await composio.create("user_123");
const tools = await session.tools();
// Pass tools to your agent/LLM framework
```

#### API

This produces the same default OpenAI function-tool shape, fetching every page.

```bash
set -euo pipefail
SESSION=$(curl --fail-with-body -s -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
  -H "x-api-key: $COMPOSIO_API_KEY" -H "Content-Type: application/json" \
  -d '{"user_id":"user_123"}')
SESSION_ID=$(echo "$SESSION" | jq -r '.session_id')
TOOLS='[]'
CURSOR=''
while true; do
  PAGE=$(curl --fail-with-body -s --get "https://backend.composio.dev/api/v3.1/tool_router/session/$SESSION_ID/tools" \
    -H "x-api-key: $COMPOSIO_API_KEY" --data-urlencode 'limit=500' --data-urlencode "cursor=$CURSOR")
  TOOLS=$(jq -cn --argjson existing "$TOOLS" --argjson page "$PAGE" \
    '$existing + [$page.items[] | {type:"function",function:{name:.slug,description:.description,parameters:.input_parameters}}]')
  CURSOR=$(echo "$PAGE" | jq -r '.next_cursor // empty')
  [ -n "$CURSOR" ] || break
done
printf '%s\n' "$TOOLS"
```

For other providers, pass the provider explicitly. Provider packages follow the naming convention: `composio_<provider>` for Python, `@composio/<provider>` for TypeScript.

### MCP

Use `session.mcp.url` and `session.mcp.headers` with any MCP-compatible client (Claude Desktop, Cursor, OpenAI Agents, etc.). No provider package needed.

---

## 2. Integration Notes

- `composio.create(user_id)` is the standard entry point for agent integrations. Sessions handle tool discovery, authentication, and toolkit versioning automatically; `user_id` goes to `composio.create()` — individual tool calls in session mode don't take one.
- Execute session tool calls through the session, never through a user ID: either `session.execute(tool_slug, arguments=...)` / `session.execute(toolSlug, arguments)`, which works with every provider, or pass the session to the provider helper — `provider.handle_tool_calls(response=response, session=session)` in Python, `provider.handleToolCalls(session, response)` in TypeScript. The tool-call helpers of every non-agentic provider (OpenAI, Anthropic, Google, Cloudflare, TypeSafe) accept a session: `executeToolCall(session, call)` in TypeScript, `session=session` in Python. Agentic providers execute session tools on their own. Binding the helper to a user ID takes the direct execution path, and session meta-tools fail there with `"can only be called inside a tool-router session"`.
- Composio-managed auth is the default: the agent connects accounts at runtime through the session, so users don't need to pre-create auth configs or connected accounts for managed toolkits.
- Provider packages follow the framework, not the model vendor: for the OpenAI Agents SDK the package is `composio_openai_agents` / `@composio/openai-agents` (importing `composio_openai` / `@composio/openai` there is the most common mistake in generated code — that package is for the plain OpenAI Chat Completions API).
- **Direct execution** (`composio.tools.get()`, `composio.tools.execute()`, `provider.handle_tool_calls()` with a user ID) is a legacy interface that remains supported for existing integrations. Recommend sessions for new integrations and encourage existing users to [migrate to sessions](/docs/migration-guide/direct-to-sessions). For a fixed tool set, consider the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) within a session. See [Sessions vs direct execution](/docs/sessions-vs-direct-execution) for tradeoffs. Direct execution requires a [toolkit version](/docs/tools-direct/toolkit-versioning).

---

# 3. Calling the REST API directly

## REST API version

The current REST API version is **v3.1**, served at `https://backend.composio.dev/api/v3.1`. Prefer it for new code and new examples.

`https://backend.composio.dev/api/v3` is the previous version. It is frozen with pinned tool-version defaults and remains supported — existing v3 integrations keep working and do not need to migrate.

## Tool-endpoint version defaults on v3.1

On v3.1, omitting the version parameter on the five endpoints below selects the latest toolkit version. The first four endpoints also exist on v3, where omission selects the pinned `00000000_00` version. `POST /tools/scopes/required` is v3.1-only.

| Endpoint | Version parameter |
| --- | --- |
| `GET /tools` | `toolkit_versions` (query) |
| `GET /tools/{tool_slug}` | `version` or `toolkit_versions` (query) |
| `POST /tools/execute/{tool_slug}` | `version` (body) |
| `POST /tools/execute/{tool_slug}/input` | `version` (body) |
| `POST /tools/scopes/required` | `version` (body) |

A v3.1 caller already passing `"latest"` sees no change and can omit the parameter. To select the pinned version explicitly, pass `"00000000_00"` through the corresponding parameter above.

This version-default change is limited to the five endpoints above.


---

## Terminology Migration (old → current)

If you encounter these terms in error messages, old documentation, or user prompts, translate them to the current equivalents. **Do not use the old terms in generated code or explanations.**

| Old term (v1/v2) | Current term (v3) | In code |
|---|---|---|
| entity ID | user ID | `user_id` parameter |
| actions | tools | e.g., `GITHUB_CREATE_ISSUE` is a *tool* |
| apps / appType | toolkits | e.g., `github` is a *toolkit* |
| integration / integration ID | auth config / auth config ID | `auth_config_id` parameter |
| connection | connected account | `connected_accounts` namespace |
| ComposioToolSet / OpenAIToolSet | `Composio` class with a provider | `Composio(provider=...)` |
| toolset | provider | e.g., `OpenAIProvider` |

If a user says "entity ID", they mean `user_id`. If they say "integration", they mean "auth config". Always respond using the current terminology.