Skip to main content

Documentation Index

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

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

​
About Aha! Ideas

Iru calls the Aha! REST API with Authorization: Bearer using a personal API key. Keys inherit the creating user’s product permissions - prefer a service account so churn does not break compliance sync.

​
How it works

Authorization: Bearer YOUR_API_KEY
DetailValue
CategoryProduct management
AuthenticationBearer (account API key)
Host pattern: https://YOUR_SUBDOMAIN.aha.io. Official references: API keys (swap subdomain), API reference.

​
Prerequisites

  • User with access to the products you must evidence (often Owner, Administrator, or Reviewer).
  • Your subdomain (acme from https://acme.aha.io).

​
Connect Aha! to Iru

​
Aha!

1

Generate an API key

Avatar → Settings → Personal → Developer → API keys → Generate API key. Name it (for example Iru Compliance), copy once.

​
Iru Compliance

1

Open Sources

In Iru Compliance, on the left navigation bar, expand Compliance and select Sources.
Left navigation: Compliance expanded, Sources selected
2

Turn on Aha!

Find Aha! (use Category or Search by name or description). On that card, turn on the toggle. A browser tab or window may open for the connector wizard.
3

Enter domain (subdomain)

Set domain to the subdomain only (for example acme), not the full URL. Confirm server variables when the wizard shows a preview.
4

Paste token and activate

Paste the Bearer token when prompted. Submit until the Aha! card shows Active.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
User deactivated or key deleted - regenerate from active service account.
Wrong subdomain string.
Issuing user lacks workspace access - adjust Aha! membership or key owner.

​
See also