About Aha! Ideas
Iru calls the Aha! REST API withAuthorization: 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
| Detail | Value |
|---|---|
| Category | Product management |
| Authentication | Bearer (account API key) |
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(acmefromhttps://acme.aha.io).
Connect Aha! to Iru
- Aha!
- Iru Compliance
Complete this tab before you connect the source in Compliance.
Open personal settings
Choose Settings, then open the Personal section (or equivalent) so you are editing your own account, not only a single product.
Open Developer and API keys
Select Developer (or Developer settings), then API keys (labels can vary slightly by Aha! edition).
Generate a new API key
Select Generate API key (or Create API key). Enter a name you will recognize later, such as Iru Compliance.
Continue on the Iru Compliance tab.
Troubleshooting
Nothing opens when you turn the source on
Nothing opens when you turn the source on
Check pop-up blocker settings for the Iru site and try again.
401 Unauthorized
401 Unauthorized
404 host
404 host
Wrong subdomain string.
Missing products
Missing products
Issuing user lacks workspace access - adjust Aha! membership or key owner.
Related Articles
Sources Management
Browse and manage every Compliance source.
Getting Started With Compliance
Frameworks, actions, and Artifacts.
Iru Overview
How Endpoint, Compliance, and Identity fit together.
Artifacts Management
Upload, review, and organize evidence from sources and actions.
