sentry-app-setup

To set up a Sentry internal integration without OAuth, create the integration in your browser, generate an auth token, and store it in the credential vault so the assistant can access Sentry APIs as itself using a Bearer header.

Sentry internal integrations require least-privilege permissions for automated issue and event reads, optional project access, and release and alert management to ensure the assistant operates securely under your organization's existing permissions.

Sentry API verification returns 401 or 403 errors when the stored auth token lacks sufficient organization permissions or is invalid, requiring you to verify org access via the /api/0/organizations/{org_slug}/ endpoint and resolve common token issues.

Yes, you can verify Sentry organization access by sending the stored auth token as a Bearer header to the /api/0/organizations/{org_slug}/ endpoint, which validates connectivity, checks permissions, and guides resolution for common 404 issues.

Configuring Sentry API access applies to organization owners and managers who need automated issue reads, release management, and alert handling, ensuring the assistant's internal integration is set up with correct least-privilege permissions.