Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 23:30 UTC
docs: update documentation for new changelog entries
github-actions[bot] committed
Apr 24, 2026 at 07:54 UTC
36f23a01b223420c938895ddabadf207c9d64902
4 files changed
+18
-6
.codex
docs/content/docs/cli.mdx
+7
-3
@@ -164,13 +164,17 @@ Use `run` when you want loops, conditionals, `Promise.all`, `search()` inside a
164
165
## Call raw APIs with proxy
166
167
-Use `composio proxy` when you want authenticated access to a toolkit API endpoint directly rather than going through a dedicated Composio tool.
167
+Use `composio proxy` when you want authenticated access to a toolkit API endpoint directly rather than going through a dedicated Composio tool. The command uses your linked account for the toolkit you pass with `--toolkit`.
168
169
```bash
170
-composio proxy https://gmail.googleapis.com/gmail/v1/users/me/profile --toolkit gmail
171
-composio proxy https://gmail.googleapis.com/gmail/v1/users/me/drafts --toolkit gmail -X POST -H 'content-type: application/json' -d '{"message":{"raw":"..."}}'
170
+composio proxy /gmail/v1/users/me/profile --toolkit gmail
171
+composio proxy /gmail/v1/users/me/drafts --toolkit gmail -X POST -H 'content-type: application/json' -d '{"message":{"raw":"..."}}'
172
```
173
174
+<Callout type="warn">
175
+Prefer relative endpoints. If you pass an absolute URL, it must stay on the same scheme and registrable domain as the toolkit account's base URL.
176
+</Callout>
177
+
178
Use `proxy` when:
179
180
- there is no dedicated tool for the endpoint you need
docs/content/docs/toolkits/custom-tools-and-toolkits.mdx
+4
-2
@@ -214,6 +214,8 @@ composio = Composio(api_key="your_api_key")
214
215
An extension tool wraps a Composio toolkit's API with custom business logic. It inherits auth via `extendsToolkit` / `extends_toolkit`, so `ctx.proxyExecute()` / `ctx.proxy_execute()` handles credentials automatically.
216
217
+Prefer relative `endpoint` values in proxy calls. They resolve against the toolkit base URL. Absolute URLs are only accepted when they stay on the same scheme and registrable domain as that base URL.
218
+
219
<Tabs groupId="language" items={['TypeScript', 'Python']} persist>
220
<Tab value="TypeScript">
221
```typescript
@@ -235,7 +237,7 @@ const sendPromoEmail = experimental_createTool("SEND_PROMO_EMAIL", {
237
238
const res = await ctx.proxyExecute({
239
toolkit: "gmail",
238
- endpoint: "https://gmail.googleapis.com/gmail/v1/users/me/messages/send",
240
+ endpoint: "/gmail/v1/users/me/messages/send",
241
method: "POST",
242
body: { raw },
243
});
@@ -278,7 +280,7 @@ def send_promo_email(input: PromoEmailInput, ctx):
280
281
res = ctx.proxy_execute(
282
toolkit="gmail",
281
- endpoint="https://gmail.googleapis.com/gmail/v1/users/me/messages/send",
283
+ endpoint="/gmail/v1/users/me/messages/send",
284
method="POST",
285
body={"raw": raw},
286
)
docs/content/docs/tools-direct/executing-tools.mdx
+7
-1
@@ -254,7 +254,13 @@ The examples above configure toolkit versions at SDK initialization. You can als
254
255
You can proxy requests to any supported toolkit API and let Composio inject the authentication state. This is useful when you need an API endpoint that isn't available as a predefined tool.
256
257
-The `endpoint` can be a relative path or absolute URL. Composio uses the `connected_account_id` to determine the toolkit and resolve relative paths against the appropriate base URL.
257
+Proxy execute requires auth context. Pass `connected_account_id` / `connectedAccountId`, or provide `custom_connection_data` if you're supplying auth manually.
258
+
259
+The `endpoint` can be a relative path or absolute URL. Relative paths are resolved against the connected account's base URL. Absolute URLs are only accepted when they use the same scheme and registrable domain as that base URL. Cross-subdomain requests on the same registrable domain still work.
260
+
261
+<Callout type="warn">
262
+Prefer relative endpoints when possible. They resolve against the connected account's base URL and avoid same-domain validation issues.
263
+</Callout>
264
265
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
266
<Tab value="Python">