Security, API, and platform updates
A summary of recent security, API, and platform changes you may need to act on. Most won’t apply to you, so skim for the ones that do. We are continuing to ship more.Legacy MCP Config routes
- MCP requests now require an API key or
Authorization: Bearertoken. We recommend moving tocomposio.create
API Keys
- IP whitelisting, choose which ip address can work from your api keys.
- Scoped API Key are slowly being rolled out with first preset for
proxyExecute. You will be able to control what actions your api keys can take.
Proxy Execute
- Proxy Execute is disabled on
v3api, please usev3.1or update your sdks. - Proxy Execute is now an opt-in capability on an API key, it is a superset of regular capabilities + proxy execute.
- Proxy Execute requests have a 250MB payload cap.
Connections
- Connected-account tokens are redacted in API responses, for both Composio-managed and custom auth configs. Please use Proxy Execute instead. If you need this for some special case please reach out to support.
- Reiterating: Composio-managed OAuth connections are moving from
initiatetolink. The cutover for remaining organizations is July 3, 2026.
Workbench
- Code execution through the remote workbench (
COMPOSIO_REMOTE_WORKBENCH,COMPOSIO_REMOTE_BASH_TOOL) now runs only inside a Composio session. If your code execution stopped working, run it within a Composio session.
Webhooks
- Webhook URLs must be publicly reachable; internal and loopback targets are now rejected.
- Deliveries are now signed (verify the
webhook-signatureheader), and there is a newcomposio.trigger.disabledevent. Manage subscriptions with the Webhook Subscriptions API.
Rate limits
- Per-IP rate limits now apply; requests that exceed them receive
429responses.
Endpoints
- The legacy v1 and v2 endpoints, deprecated last year, have now been removed. Any calls to
/v1orv2endpoints now return410, please use the class ofv3andv3.1endpoints, if you need a guide to migration you can use this