Skip to main content
Telara

Integrations / Opsgenie

Opsgenie logo

Opsgenie

Opsgenie alerting and incident management — alerts, incidents, on-call schedules, escalations, teams, and heartbeat monitors.

API key
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

An Opsgenie account (or Jira Service Management Ops) you can administer.
Permission to add an API integration on the team Telara should see.

Vendor setup

Get the credential

1
Add an API integration
In Opsgenie, Settings → Integrations → Add → API. Create it on the team whose alerts Telara should see. Copy the key.
2
Paste in Telara
Settings → Integrations → Opsgenie.

In Telara

Connect in Telara

API key

Opsgenie API integration key. Create one under Settings > Integrations > add "API" integration in your Opsgenie team, then send it as the Authorization header value "GenieKey <key>" (verified against the official Opsgenie OpenAPI spec's securityDefinitions, which names the header scheme "GenieKey" and puts the token in the Authorization header; the literal "GenieKey " prefix text itself is Opsgenie's documented convention, not something the spec's securityDefinitions block spells out character-for-character). EU-hosted accounts must also store base_url as https://api.eu.opsgenie.com with the credential — the engine uses a stored base_url field to override api.base_url per credential (same mechanism PostHog's EU Cloud override uses).

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key

Knowledge

What gets indexed

ResourceCoverage
TeamPartial — not every record the vendor holds is synced
SchedulePartial — not every record the vendor holds is synced
UsersPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
TeamUp to 1 dayRemoved records disappear on the next full sync
ScheduleUp to 1 dayRemoved records disappear on the next full sync
UsersUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Team, Schedule, Users.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A global API key from a different team will not see that team’s alerts.
Atlassian-region host mismatch (US vs EU) looks like a bad key.