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.

redirect uri

Sushmithamallesh2c5dfffe6e4b
diff --git a/fern/pages/src/authentication/programmatic-auth-configs.mdx b/fern/pages/src/authentication/programmatic-auth-configs.mdx
index b46350b49..c723f722a 100644
--- a/fern/pages/src/authentication/programmatic-auth-configs.mdx
+++ b/fern/pages/src/authentication/programmatic-auth-configs.mdx
@@ -69,6 +69,7 @@ auth_config = composio.auth_configs.create(
"credentials": {
"client_id": "1234567890",
"client_secret": "1234567890",
+ "oauth_redirect_uri": "https://backend.composio.dev/api/v3/toolkits/auth/callback",
},
},
)
@@ -81,6 +82,7 @@ const authConfig = await composio.authConfigs.create("NOTION", {
credentials: {
client_id: "1234567890",
client_secret: "1234567890",
+ oauth_redirect_uri: "https://backend.composio.dev/api/v3/toolkits/auth/callback",
},
authScheme: "OAUTH2",
});
@@ -89,6 +91,10 @@ console.log(authConfig);
```
</CodeGroup>
+<Note>
+You can specify a custom redirect URI by including the `oauth_redirect_uri` parameter in the credentials object. If not provided, Composio uses the default redirect URI.
+</Note>
+
**Specifying the authorized redirect URI**
The process of setting up your own OAuth2 credentials usually involves generating a client ID and secret and specifying the **authorized redirect URI** in the OAuth configuration.