Integrations Error & Oauth Scopes
So I'm building an integrations view on my app where users can see all available apps on composio (and then connect to whichever ones they choose).
My first issue, is that I wrote a simple script to loop through all apps (using
client.apps.list()) so I can bulk create integrations to display on the integrations page. For every app, I'm calling client.integrations.create({ ...params }) but over half of these iteration attempts return an error with the message: "API not found for https://backend.composio.dev/api/v1/integrations".
Is there a better way of doing this? or a REST endpoint that returns better results (instead of using the TS SDK)?
Seems like a handful of apps are not "integrate-able".
My next question is scopes.
Seems like my mental model for integrations is off. I view an integration as an "application-scoped" resource - something I create one time for each app. I then assumed that I can have a multiple accounts for each integration and those are entity-scoped resources.
Seeing that oauth scopes are added at the integration-creation step, it seems like the best way to accommodate entity-specific oauth scopes is to create "multiple integrations" per entity.
Instead of trying to connect the same integration-instance to each entity.
Hope my question makes sense.1 Reply
adverse-sapphire•2mo ago
You can get all the apps via API, check this docs and lemme know if it works or not:
https://docs.composio.dev/api-reference/apps/list-apps
And for second question can you try to give some more context??
Composio Docs
List apps - Composio
Composio enables your agents to connect with Various Tools and work with them