Composio Platform API

Name: Composio Platform API API
Brand: Composio Platform API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi CdapiKey86 EndpointsREST

For Agents

Connect AI agents to third-party SaaS tools through Composio: link accounts, configure auth, execute toolkit actions, subscribe to triggers, and inspect logs.

Quickstart

Get started with Composio Platform API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"connect a user account to a SaaS tool through Composio"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Composio Platform API API.

Link a user account to a third-party SaaS toolkit through a hosted OAuth flow

Execute a toolkit action against a connected account on behalf of an agent

Subscribe to triggers so an external SaaS event invokes an agent webhook

Manage auth configurations so multiple agents share one OAuth client per toolkit

GET STARTED

Start building with Composio Platform API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Composio Platform API API for, with concrete tasks.

★ Multi-Tool Agent Account Linking

Give end-users a single onboarding flow that connects their Slack, Gmail, GitHub, and Notion accounts to your agent. The /api/v3/auth_configs endpoints define reusable OAuth clients, /api/v3/connected_accounts manages each user's linked account, and /api/v3/connected_accounts/link returns a hosted link the user follows to grant consent. Agent builders use this to skip building per-vendor OAuth flows.

Create a connected-account link for user u_42 to connect their Gmail, then poll /api/v3/connected_accounts/{nanoId}/status until it reports active

Tool Execution from an LLM

Run a toolkit action selected by the LLM against the user's connected account. Composio handles the auth injection, parameter validation, and response normalization so the agent only needs to choose the action and pass the inputs. This removes the integration burden when an agent's plan involves multiple SaaS tools in a single chain.

Execute the slack_send_message tool with channel #ops and text 'Deployment complete' on behalf of connected account ca_8821

Event-Driven Agents via Triggers and Webhooks

Wake an agent on real-world events such as a new email, a Stripe charge, or a GitHub PR. Triggers subscribe to upstream SaaS events and Composio forwards them to a webhook subscription registered at /api/v3/webhook_subscriptions with a rotatable secret. Engineering teams use this for incident-response and notification agents that should not poll.

Subscribe a webhook with URL https://app.example.com/hooks for github_pull_request_opened events and rotate its signing secret

Operations and Debugging

Inspect why an agent run failed by pulling structured logs of action executions and trigger deliveries. /api/v3/internal/action_execution/logs and /api/v3/internal/trigger/logs return the inputs, outputs, and errors for each call. Platform teams use these endpoints to build observability dashboards over agent activity.

Retrieve the last 50 action execution log entries and return the ones whose status is not 'success'

Agent-Driven Composio Operations via Jentic

Let an AI assistant manage Composio itself: provision projects, rotate API keys, and audit connected accounts. Through Jentic the agent searches by intent, loads the schema for the relevant Composio operation, and executes the call without the developer wiring auth or pagination. This is useful for platform teams running many agents on Composio.

On the prompt 'rotate the api key for project nano_77 and report the new key fingerprint', call the regenerate-api-key endpoint and return the rotated key prefix

Key Endpoints

86 endpoints — the composio platform api powers composio's tool-use platform for ai agents.

METHOD

PATH

DESCRIPTION

POST

/api/v3/connected_accounts/link

Generate a hosted link to connect a third-party account

GET

/api/v3/connected_accounts

List connected accounts

GET

/api/v3/connected_accounts/{nanoId}/status

Check the status of a connected account

POST

/api/v3/auth_configs

Create a reusable auth configuration for a toolkit

POST

/api/v3/webhook_subscriptions

Create a webhook subscription

POST

/api/v3/webhook_subscriptions/{id}/rotate_secret

Rotate the signing secret for a webhook

GET

/api/v3/internal/action_execution/logs

Inspect recent action execution logs

GET

/api/v3/internal/trigger/logs

Inspect recent trigger delivery logs

POST

/api/v3/connected_accounts/link

Generate a hosted link to connect a third-party account

GET

/api/v3/connected_accounts

List connected accounts

GET

/api/v3/connected_accounts/{nanoId}/status

Check the status of a connected account

POST

/api/v3/auth_configs

Create a reusable auth configuration for a toolkit

POST

/api/v3/webhook_subscriptions

Create a webhook subscription

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Composio API keys (project, org, and user) are stored encrypted in the Jentic vault and injected as the correct x-*-api-key header at execution time. The raw key never enters the model context or application logs.

Intent-based discovery

Agents search Jentic with intents like 'connect a user account to a SaaS tool' and Jentic returns the matching Composio operation with its parameter schema, so the agent can call POST /api/v3/connected_accounts/link without browsing developer docs.

Time to first call

Direct integration: 1-2 days to wire auth configs, link flows, action execution, and webhook signing. Through Jentic: under 1 hour via search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Pipedream

Workflow platform that brokers OAuth and exposes thousands of SaaS actions

Choose Pipedream when you want a workflow-engine model with hosted code steps in addition to brokered OAuth and actions.

Alternative

Zapier Natural Language Actions

Zapier's NLA endpoint that exposes Zapier actions to AI agents

Choose Zapier NLA when your users already live in Zapier and you want to reuse their existing connected apps and actions.

Complementary

Anthropic Messages

Claude chat completions with native tool-use support

Use Anthropic Messages as the LLM that decides which Composio toolkit action to call next.

FAQs

Specific to using Composio Platform API API through Jentic.

What authentication does the Composio Platform API use?

The API supports several API-key headers depending on context: x-api-key for project keys, x-org-api-key for organization-scoped calls, x-user-api-key for user-scoped calls, and a cookie-based authToken for the dashboard session. Through Jentic the appropriate key is stored encrypted in the vault and injected at execution time.

Can I link a user's third-party account with the Composio API?

Yes. Create an auth config via POST /api/v3/auth_configs for the toolkit you want, then call POST /api/v3/connected_accounts/link to generate a hosted link the user follows to grant consent. The resulting connected account is referenced by its nanoid in subsequent action calls.

How do I execute a toolkit action through the Composio API?

Resolve the action under the Tools resource, then submit its inputs against the user's connected account. Composio injects the connected-account credentials, validates inputs against the action schema, and returns a normalized response that the agent can pass back to the LLM.

What are the rate limits for the Composio Platform API?

Composio applies plan-tier rate limits with bursts handled per project key. The free tier is in the low hundreds of requests per minute and paid tiers scale up; agents should respect HTTP 429 responses, which Jentic surfaces as structured errors rather than retrying silently.

How do I subscribe to a SaaS event through Jentic?

Run the Jentic search query 'subscribe to a Composio trigger', load the returned operation (POST /api/v3/webhook_subscriptions), and execute it with the URL, event types, and secret. Rotate the secret periodically via POST /api/v3/webhook_subscriptions/{id}/rotate_secret.

Can I inspect why an action execution failed?

Yes. GET /api/v3/internal/action_execution/logs returns the recent execution log entries with inputs, outputs, and error details. GET /api/v3/internal/action_execution/log/{id} fetches a single entry for deep inspection.