Aha!

Connect Aha! to collect ticketing evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Aha!:

   1. Sign in to Aha!.
   2. Open the API keys settings page (https://secure.aha.io/settings/api_keys) and generate an API key.

   Where to find the other values:

   • Subdomain: The part before .aha.io in your account-specific domain (<yourcompany>.aha.io); the API must be accessed on this domain.

   Aha!'s public documentation does not cover every step.

   The API docs link to the API keys page but don't give the menu path, button labels, or whether the key is shown once. The key acts as the user who created it.

   Source: aha.io, checked 2026-10-07.

   The permissions Safeguard needs. Aha! shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it.

2. On Compliance › Connectors, open Aha!, click Connect, choose API token and fill in:

   Field	What to enter
   Subdomain	Required. The part before .aha.io in your address.
   API key	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Aha! and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Ticketing connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks