Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Connect your users to Sentry for error monitoring, performance tracking, and project management.
PropertyValue
Provider IDsentry
PKCESupported
Token refreshAutomatic (refresh token reused)
Access token lifetime30 days
Redirect URIShown in Developer Portal

​
Step 1: Create a Sentry OAuth Application

1

Go to Sentry API Applications

Navigate to sentry.io and go to Settings > Account > API > Applications, or go directly to sentry.io/settings/account/api/applications/.
2

Create a new application

Click Create New Application and select Confidential as the application type.Fill in:
  • Name: The application name (e.g., “My App”)
  • Redirect URIs: Copy the Redirect URI from the Developer Portal
3

Configure scopes

Select the required scopes for the application. See Available Scopes below.
4

Get credentials

After saving:
  • Client ID: Displayed on the application page
  • Client Secret: Displayed on the application page
Copy both values.

​
Step 2: Add to Alter Vault

1

Open the Developer Portal

Go to portal.alterauth.com and navigate to your app.
2

Add Sentry provider

Go to OAuth Providers > Add Provider > Sentry.
3

Enter credentials

  • Client ID: Paste your Sentry Client ID
  • Client Secret: Paste your Sentry Client Secret
4

Select scopes

Choose the scopes your app needs.
5

Save

Click Save. The provider is now active.

​
Step 3: Test It

After a user connects via Alter Connect, use the returned grant_id to make API calls: 
from alter_sdk import AlterVault, HttpMethod

async with AlterVault(
    api_key="alter_key_...",
    caller="my-agent",
) as vault:
    response = await vault.request(
        HttpMethod.GET,
        "https://sentry.io/api/0/organizations/",
        grant_id=grant_id,
    )
    orgs = response.json()
    for org in orgs:
        print(f"{org['name']} ({org['slug']})")

​
Available Scopes

Sentry scopes follow a hierarchy: admin > write > read. Requesting a higher level automatically includes lower levels.

​
Organization

ScopeDescription
org:readRead organization data
org:writeModify organization information
org:adminFull organization control including deletion

​
Project

ScopeDescription
project:readView project details
project:writeCreate or modify projects
project:adminFull project management including deletion
project:releasesManage project and organization releases

​
Team

ScopeDescription
team:readView team information
team:writeCreate or modify teams
team:adminFull team management including deletion

​
Member

ScopeDescription
member:readView member details
member:writeAdd or modify members
member:adminFull member management including deletion

​
Event

ScopeDescription
event:readView issues and events
event:writeModify issues
event:adminDelete issues

​
Common API Endpoints

Use CaseMethodURL
List organizationsGEThttps://sentry.io/api/0/organizations/
List projectsGEThttps://sentry.io/api/0/organizations/{org_slug}/projects/
List issuesGEThttps://sentry.io/api/0/projects/{org_slug}/{project_slug}/issues/
Get issue detailsGEThttps://sentry.io/api/0/issues/{issue_id}/
List releasesGEThttps://sentry.io/api/0/organizations/{org_slug}/releases/
Resolve an issuePUThttps://sentry.io/api/0/issues/{issue_id}/

​
Notes

  • Access tokens expire after 30 days. Alter Vault automatically refreshes them using the refresh token.
  • Sentry’s refresh token is reused (same token persists across refreshes), similar to Google’s pattern.
  • Sentry scope permissions in the application settings must match the scopes requested. If a scope that the application doesn’t have permission for is requested, the authorization will fail.
  • The default scopes (org:read, project:read, team:read, event:read) provide read-only access, which is sufficient for most monitoring use cases.