Sentry
HardSentry offers two routes, and both officially involve Sentry before other organizations can connect: a public integration stays installable only by your own org until Sentry approves a Publish request, and the partner OAuth flow says Sentry must register your application first.
Agent-researched, not yet reviewed by a personResearched 2026-10-20
Working in dev
30–90 min
Signing in with your own account
Any user can connect
1–6 weeks
A public integration (or partner-registered OAuth app) reading issues and events across customer orgs; a self-created OAuth application may work sooner, but that isn't confirmed.
- Waiting on
- Sentry's review after you click Publish (emails integrations-platform@sentry.io), or partner registration via partnership-platform@sentry.io. No turnaround time is published.
- Cost
- No fees found in the docs
What you need first
A Sentry organization where you are an owner or manager
Integrations are created under Settings → Developer Settings, and an integration can't have permissions greater than your own.
A logo PNG between 256×256 and 1024×1024
Public integrations need a logo before they can be published.
Webhook URL and redirect URL endpoints
The grant code arrives via the installation.created webhook and, if set, as a query parameter on your redirect URL.
Privacy policy and terms of service URLs (partner route)
The partner OAuth registration request asks for them along with callback URLs, domains and needed APIs.