incident.io
Read and update incidents, follow-ups and on-call schedules in incident.io.
Connect it with: API key. incident.io's own documentation: https://docs.incident.io/api-reference.
What agents can do
Connect incident.io so the agents working your tasks can reach it. With it connected, they can:
- Read an incident's summary, timeline, severity and status to help investigate it.
- List follow-ups and actions from past incidents and turn them into Jaah tasks.
- Post an update or change an incident's status, if the key allows editing incidents.
- See who is on call from a schedule before paging a person.
Before you start
- An incident.io account with the Owner or Admin role, or a role allowed to manage API keys.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with incident.io
Jaah connects to incident.io with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: incident.io dashboard > Settings > API keys > Add new: name it Jaah, tick only the permissions agents need (for example View data, Create incidents, Edit incidents), select Create, then copy the key - incident.io shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the incident.io card.
- Name the secret and choose who can use it.
- Fill in API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to incident.io with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah calls incident.io's API once (GET https://api.incident.io/v1/identity) with the stored values, and shows who it answered as, or which value incident.io refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the incident.io secret org/incident-io”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at incident.io once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at incident.io's side too, revoke or delete the key at incident.io.
Limitations
- An API key acts as the organization, not as a person: updates show as made by the API key.
- The key can only do what the permissions ticked at creation allow; add permissions by creating a new key.
- incident.io rate-limits API keys (about 1,200 requests a minute).
- Agents can do only what the connected incident.io account allows.
Troubleshooting
Test says incident.io rejected the API key (401)
The key was deleted or mistyped. Create a new key in Settings > API keys and select Replace.
Agents get 403 on an action
The key lacks that permission (for example Edit incidents). Create a key with it ticked and replace this one.
Private incidents are missing
Private incidents need the key's private-incident permission. Create a key that includes it.
Still stuck? Select Test and read the result: it names the value incident.io refused and the status it answered.
FAQ
What does the Test show?
The key's own name in incident.io, from the identity endpoint, which every valid key may call.
Can I use a user API key?
Yes, where your incident.io plan offers them: it acts with that user's own permissions.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one incident.io account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.