Skip to main content
An OAuth app lets your product (a CRM, helpdesk, sales tool, or any service with its own users) connect to Sight AI on behalf of Sight AI customers. The customer clicks “Connect Sight AI” in your product, approves a consent screen, and your app receives a token scoped to their team.
This page is for apps that other Sight AI customers will connect to. If you only want to use Sight AI from Claude, Cursor, or another MCP client yourself, you don’t need any of this: see MCP Setup.

​
How it works

  1. A team owner or admin registers the app in Integrations → Sight AI API → OAuth apps.
  2. The app starts in development: owners and admins of the team that registered it can authorize it, so you can build and test end to end.
  3. You submit the app for review. Sight AI reviews it and either approves it or asks for changes.
  4. Once approved, any Sight AI team can authorize it.
Nothing about your client_id, secret, or redirect URIs changes between statuses, so the integration you test in development is exactly what customers use after approval.

​
Register the app

  1. Sign in to Sight AI as a team owner or admin.
  2. Open Integrations → Sight AI API → OAuth apps.
  3. Enter a client name your customers will recognize on the consent screen (for example Acme CRM) and your HTTPS redirect URI (for example https://acme.com/oauth/sightai/callback).
  4. If your app has a backend that can keep a secret, check Server-side app (issue a client secret). Copy the client_secret (sai_ocsec_…) immediately; it is shown once. Leave the box unchecked for SPAs and desktop apps, which use PKCE alone. See Public vs. confidential clients.
  5. Click Create OAuth client and copy the client_id.
The authorization code flow (PKCE required for every client) is documented in Authentication and walked through end to end in Webhooks → The OAuth flow.

​
Build and test in development

While the app is in development, start the flow from your product while signed in to Sight AI as an owner or admin of the team that registered it. The consent screen shows only that team; anyone else who reaches the screen sees that the app has not been approved yet and cannot continue. Use this phase to confirm:
  • The redirect URI you registered matches the one your app sends, exactly (loopback URIs ignore the port; everything else must match character for character).
  • Your app requests only the scopes it needs. Reviewers compare the scopes to what the app says it does.
  • Token refresh works, and revoking the app from the OAuth apps page disconnects it cleanly.

​
Submit for review

On the OAuth apps page, click Submit for review next to the app. You’ll be asked for: What we check:
  • Redirect URIs are HTTPS and belong to a domain you control. Loopback URIs are fine for desktop apps.
  • Scopes match the purpose. An app that only reads analytics should not request inbox:write.
  • Customers can identify and reach you. The client name matches your product, the homepage is live, and the support contact works.
  • Confidential where possible. Apps with a backend should register as server-side apps so a leaked refresh token can’t be redeemed without the secret.
Reviews are usually completed within a few business days. You get a confirmation email when you submit, and we reply on that same request if we need anything, so answering the email is enough. The outcome arrives by email either way, and the app’s status updates on the OAuth apps page. If we request changes, the notes appear on the OAuth apps page. Fix the issues and click Resubmit for review; your previous answers are prefilled.

​
After approval

  • Any Sight AI team owner or admin can now authorize the app from your connect flow.
  • Keep your client secret private and rotate it if it is ever exposed.
  • If the app’s purpose, scopes, or redirect domain change materially, let us know at support@trysight.ai so the review stays accurate.
  • Sight AI can withdraw approval if an app behaves differently from its submission. The registering team keeps development access; tokens granted by other teams are revoked immediately, and you receive an email explaining why.

​
Revoking an app

Revoking an app from the OAuth apps page deactivates its client_id, revokes every token it holds across all teams, and deletes any webhook subscriptions it created. Customers who want to disconnect just your app can revoke their own authorization from Integrations → Sight AI API on their side.

​
FAQ

Do Claude, Cursor, or other MCP clients need review? No. They register themselves through dynamic client registration and are only ever authorized by the person who started the connection. Review applies to apps registered from the dashboard that other customers will connect to. I admin several Sight AI teams. Can they all use my in-development app? Only the team that registered the app can authorize it before approval. Register and test from one team, then submit for review. Can I test with a real customer before approval? Not directly. Invite them as an admin on your registering team for the test, or submit for review first. Development access is intentionally limited to the registering team so unreviewed apps can’t be used to collect tokens from other customers. What happens to existing customers if changes are requested later? Approval is only withdrawn for cause, and we email you before or as it happens. Tokens from other teams are revoked at that point; your own team’s access continues.