Integration guide
2 min read
Connect Sentry
Add optional quality context with a dedicated read token.
Before you start
- A Sentry organization with the projects you want to connect.
- Permission to create an internal integration in Sentry.
- Owner or admin access in Specita.
Set up the connection
Create an internal integration
In Sentry organization Settings → Developer Settings → Internal Integrations, create a dedicated integration for Specita.
Select read permissions
Enable Organization read, Project read, and Event read only. Do not add write, admin, or member-management permissions.
Connect the token
Copy the integration token into Specita → Integrations → Sentry. The form validates access before storing it.
Attach the project
Map the intended Sentry project to the correct Specita product. Quality shows project-wide context, not release attribution.
Link the SDK release
Open a platform release with a successful delivery → Runtime evidence → Link SDK release. Confirm the full SDK release tag and SDK environment for that delivery. Link the previous version too, then refresh evidence. Specita checks exact identities; it does not guess from the display version.
Check your setup
- The connection is active and the correct project is mapped.
- The release shows exact SDK tags, observation windows, recorded-session counts, and issue-event links.
- Missing tags, low samples, or incompatible baselines show unknown rather than a health verdict.
Troubleshooting
Token rejected
Check the three read permissions, the Sentry organization, and token revocation. The current connection supports sentry.io, not a custom self-hosted API origin.
No Sentry in our stack
Skip this integration. It is optional and is not required to track or review releases.
Credential safety
Use a dedicated token and revoke it in Sentry if exposed. Do not put tokens in release notes, Slack, screenshots, or source control.