Skip to main content
Projects are Composio’s multi-tenancy primitive. Every Composio account belongs to an organization. Inside an organization, projects are isolated environments that scope your API keys, connected accounts, auth configs, and webhook configurations. Resources in one project are not accessible from another. Common reasons to use multiple projects:
  • Separate environments: keep production and staging isolated
  • Separate products: keep resources for different apps independent
  • Client isolation: give each client their own project with separate credentials and data

Managing projects

Manage projects from the dashboard or via the API using an organization API key (x-org-api-key).
Project management endpoints use the x-org-api-key header, not the regular x-api-key. Find your org API key in the dashboard under Settings > Organization.
There is no limit on the number of projects per organization. Project names must be unique within the organization. Create a project with should_create_api_key: true to get an API key back in the response: The Python SDK also needs COMPOSIO_API_KEY to initialize. Its generated organization client selects the organization key for this operation.
The list endpoint supports pagination with limit and cursor; getting a project by ID returns the full project object including its API keys.

Project settings

Each project has settings that control security, logging, and display behavior. The project detail endpoints return current configuration for inspection. Use Settings > Project Settings in the dashboard to update project settings. Notable security setting: require_mcp_api_key, when true, requires MCP server requests to include a valid x-api-key header. This defaults to true for organizations created on or after March 5, 2026.

Get project details by ID With Org Api key

Retrieves detailed information about a specific project using its unique identifier. This endpoint provides complete project configuration including webhook URLs, creation and update timestamps, and webhook secrets. Use this endpoint to inspect project settings or verify project configuration.

List all projects

Retrieves all projects belonging to the authenticated organization. Projects are returned in descending order of creation date (newest first). This endpoint is useful for displaying project selection in dashboards or for integrations that need to list all available projects.

List all projects

Retrieves projects belonging to the authenticated organization by default, or all organizations the authenticated user belongs to when list_all_org_projects is true. Projects are returned in descending order of creation date (newest first). This endpoint is useful for displaying project selection in dashboards or for integrations that need to list all available projects.

Delete and generate new API key for project

Generates a new API key for the specified project, invalidating any existing API keys for that project. This operation creates a fresh API key with a new random name and key value. Every existing API key for the project stops working immediately.

Create a new project

Creates a new project within the authenticated user's organization using the specified name. Projects are isolated environments within your organization, each with their own API keys, webhook configurations, and resources. Use this endpoint to create additional projects for different environments (e.g., development, staging, production) or for separate applications.

Project usage breakdown

Grouped metering usage breakdown for the authenticated project. Groups results by a single dimension or column key.

Project usage summary

Aggregated metering usage for the authenticated project only. Values are summed from raw metering events grouped by `entity_type`.

Delete a project

Deletes a project within the organization by its unique identifier. This affects every resource belonging to the project, including its API keys, webhook configurations, and connected services. The action cannot be undone. Pass `?revoke_on_delete=true` to also revoke the upstream credentials of every connection in the project.