Docs · Connect your tools
Connect Opsgenie
StackWeaver reads, and never changes, one read-only endpoint on your Opsgenie account once a day, through an API key you create yourself. This guide says exactly what is read, which permission the key needs, how to create one, and how to remove it.
Last reviewed: 6 November 2026 · Describes what is live in production on that date. A result is evidence of what the provider returned at a time, nothing more.
1. What it collects
Once a day StackWeaver calls Opsgenie's API with the key you paste. The result is kept as an Evidence Object with a SHA-256 fingerprint (platform), including a result that fails.
| Check (as shown in the portal) | What it looks at |
|---|---|
| API key valid and reachable | Whether the stored key is accepted and Opsgenie's own account endpoint responds with your account name, user count and plan. Evidence only: no threshold is applied. |
2. What it does not do
- It never reads an alert, incident or schedule. The one check reads only your account's own name, user count and plan.
- It cannot change anything: the key is used for one read-only endpoint.
- It does not say your incident-response programme meets any requirement. A result is what Opsgenie returned at a certain time.
- It works against either the default (US) Opsgenie instance or the EU instance; you say which when you connect.
3. The access it needs
One credential: an API key, sent as `Authorization: GenieKey <API_KEY>` on every request (Opsgenie).
Who can connect. In StackWeaver, a workspace owner or admin pastes the key. Opsgenie does not tell StackWeaver who created the key or what role they hold, so create it with no more access than this one read-only check needs.
4. Connect steps
- In Opsgenie, open Settings → API key management and create a new key.
- In StackWeaver, open Evidence, the Opsgenie section, and paste the key. Type "eu" in the region field if your account is on the EU instance, or leave it empty for the default instance.
- Press Test connection. StackWeaver records the result and fills in the account name automatically.
5. Reading the results
| Label | What it means |
|---|---|
| Pass | The provider returned data that meets the threshold at that time |
| Fail | The provider returned data that does not meet the threshold |
| Not enabled | There was nothing to check, or the feature needs a plan StackWeaver could not confirm |
| Could not check | StackWeaver could not read the data, or the check needs a higher plan than the account has |
6. Disconnect and revoke
- In StackWeaver, press Disconnect on the Opsgenie section. StackWeaver deletes the stored key.
- In Opsgenie, revoke or delete the key yourself — StackWeaver has no way to ask Opsgenie to revoke a key on your behalf.
What remains. Past evidence stays in your workspace as the audit trail. Disconnecting does not delete it.
7. Troubleshooting
| Message | What to do |
|---|---|
| Opsgenie refused the key: it may be wrong or revoked | Check the key was copied in full, and that the region field matches your account (a US key will not work against the EU setting, and vice versa) |
| This key belongs to a different Opsgenie account than the one already connected here | Disconnect first if you mean to switch to a different Opsgenie account |
Still stuck? Use the contact page.
Sources and method
Statements about GitHub and Okta link to their own documentation. Statements about StackWeaver link to the page that says them, or are recorded in a claims ledger with the file in StackWeaver's repository that they come from. See oureditorial policy. Spotted an error? Use the contact page.