OAuth Callbacks and Scopes

Use this page when your workspace admin or platform team needs the exact callback path and permission shape for an integration.

All callbacks use your MergeLoom controller host:

https://controller.mergeloom.ai

Callback and Scope Table

Integration	Callback	Scopes or permissions
Jira	/api/integrations/jira/callback	read:jira-user, read:jira-work, write:jira-work, offline_access
Confluence	/api/integrations/confluence/callback	read:confluence-content.all, offline_access
GitHub	/api/integrations/github/callback	GitHub App with Contents read/write, Pull requests read/write, Issues read/write when using issue intake, Metadata read-only
GitLab	/api/integrations/gitlab/callback	OAuth scope api; self-managed GitLab also needs matching base and API URLs
Azure Boards / Azure Repos	/api/integrations/azure-boards/callback	499b84ac-1321-427f-aa17-267ca6975798/user_impersonation, offline_access
monday.dev / monday.com	/api/integrations/monday/callback	me:read, account:read, workspaces:read, boards:read, boards:write, updates:read, updates:write
Linear	/api/integrations/linear/callback	read, write

Review notifications use Slack or Microsoft Teams incoming webhook URLs. They do not use an OAuth setup path in the current customer workflow.

Common Callback Problems

• the app callback URL uses the wrong controller host
• the browser is connected to one workspace but the app was installed for another
• a required scope was omitted
• the connected account cannot see the project, board, repository, or space
• a self-managed GitLab base URL and API URL do not match the same instance
• an Azure account can read Boards but cannot push to Azure Repos

After fixing a callback or scope issue, reconnect the integration and run a manual sync from the Controller UI.

Related pages:

• Integrations Overview
• Work Tracker Intake
• Code Host Output