Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

fix: replace curl example with HTTP snippet to fix gitleaks

Composioa11f300afe21
diff --git a/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx b/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
index b09b4d4f6..89142a356 100644
--- a/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
+++ b/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
@@ -31,11 +31,11 @@ Nothing changes for existing organizations. If your organization was created bef
If you need to disable API key enforcement for a new project, you can set it explicitly during project creation or update the setting afterward:
-```bash
-curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
- -H "Content-Type: application/json" \
- -H "x-api-key: ak_your_api_key" \
- -d '{"require_mcp_api_key": false}'
+```http
+PATCH /api/v3/org/project/config
+Content-Type: application/json
+
+{"require_mcp_api_key": false}
```
<Callout type="info">