Connected apps - Browser Use

Connect an app once per project with OAuth. The agent can then use it in chats you start in the Cloud app.

Runs created with an API key do not get connected-app tools yet. The endpoints below manage the project’s connections; they do not add tools to API runs.

Connect an app

Find the provider name:

curl "https://api.browser-use.com/api/v4/integrations?search=gmail" \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY"

Each item has provider, display_name, category, and is_connected. Use popular_only=true or connected_only=true to filter the list, but not both. GET /api/v4/integrations/categories lists the categories. Start OAuth and open the returned redirect_url in a browser:

curl -X POST "https://api.browser-use.com/api/v4/integrations/gmail/authorize" \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY"

After you approve access, poll until is_connected is true:

curl "https://api.browser-use.com/api/v4/integrations/gmail/status" \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY"

Disconnect an app

curl -X DELETE "https://api.browser-use.com/api/v4/integrations/gmail" \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY"

Limits

Connections belong to the project, not to one API key or session.
Zero Data Retention and PHI projects get 403 on authorize. They can still list and disconnect existing connections.
Connected apps are not available on the EU deployment.
A restricted API key needs integrations Read to list connections and check status, and Write to authorize or disconnect.

⌘I