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 Heroku
Iru reads app and dyno configuration, pipelines, add-ons, and team access metadata via the Heroku Platform API using a Bearer token (CLI authorization or account API key).How it works
| Detail | Value |
|---|---|
| Category | PaaS / developer tooling |
| Authentication | Platform API token (Bearer) |
Prerequisites
- Access to the Heroku CLI or dashboard API Key section.
- Awareness of SSO: tokens may align to shorter session windows - see Heroku docs for
--expires-in.
Connect Heroku to Iru
Heroku
Create an API token
CLI (typical): run
heroku authorizations:create --description "Iru Compliance" and copy the Token value. Default expiry is often one year; SSO orgs may see shorter lifetimes - adjust with --expires-in when policy allows.Dashboard: Account settings → API Key → Reveal or Regenerate (regeneration invalidates the prior key everywhere).Iru Compliance
Turn on Heroku
Find Heroku (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.
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
Stale after regenerate
Stale after regenerate
Dashboard regeneration invalidates old tokens - update Iru.
Missing apps
Missing apps
Token’s account must belong to the right teams.
Considerations
Iru is read-only: no deploys, scales, or restarts.
Iru is read-only - no deploys, scales, or restarts.
See also
- See Sources Management for the full connector list.
