Internal Integrations

Internal integrations are meant for custom integrations unique to your organization. They can also be as simple as an organization-wide token. Whether you are using just the API or all the integration platform features combined, internal integrations are for use within a single Sentry organization.

Internal integrations don't require an OAuth flow. You receive an org-wide auth token immediately after creation:

Diagram showing process difference between public and internal integrations.

For an example of how to build an internal integration, see our Round Robin Issue Assignment integration (or jump straight to the code on GitHub).

Installation

Creating an internal integration will automatically install it on your organization.

Auth Tokens

Internal integrations automatically generate an authentication token when configured. If you need multiple tokens, or need to get a new one, you can go to Settings > Developer Settings > [Your Internal Integration] and do so. You can have up to 20 tokens at a time for each internal integration. These tokens do not expire automatically, but you can manually revoke them as needed.

Image showing the ability to copy tokens, create new tokens, revoke tokens, and when they were created in UTC.

Image Requirements

Internal integrations don't require logos or icons to be uploaded, but you can upload them if you want to. The requirements for those are:

  • Logo size must be between 256 × 256px and 1024 × 1024px
  • File format must be PNG
  • Background must be transparent (unless the logo takes up the entire space)

If the integration has a UI component, you can also upload an icon that follows these requirements:

  • Icon size must be between 256 × 256px and 1024 × 1024px
  • File must be a PNG in RGBA format
  • All pixels must be black or transparent
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").