Connecting Opsgenie to Landfall
Opsgenie connects to Landfall in two independent directions, like Datadog and PagerDuty: Read — an API key so Landfall knows what's paging — and Trigger — an action webhook that opens a Landfall war room the moment an alert fires. You can set up either one alone, or both.
What you'll need
- An Opsgenie account with permission to create an API integration and configure action webhooks.
- An admin (owner/admin role) on your Landfall organization for both halves below.
1. Read — an API key
Opsgenie → Settings → Integrations → Add integration → API
Generate a GenieKey (API integration key). Note your account's region too — EU accounts use api.eu.opsgenie.com.
app.opsgenie.com/settings/integration/add/API
Screenshot pending — see this guide's tracked follow-up. Add it to Landfall
In Landfall, open Settings → Integrations → Opsgenie, paste the key, select your region, and run Test connection.
2. Trigger — Opsgenie opens a war room
Opsgenie's action webhook posts to Landfall's POST /triggers/opsgenie endpoint on Create, and can also Acknowledge/Close an already-open war room raised from the same alert. Every delivery is authenticated by a per-organization shared secret, checked against a header Opsgenie sends on every request — never trusted from the request body.
Issue a webhook secret
This step doesn't have a button in the app yet — an owner/admin issues it via the API:
Request POST /o/<your-org-slug>/triggers/opsgenie-secret Auth Your normal Landfall session/API token, owner or admin role Response 200 { "secret": "<64 hex characters>" } The secret is shown once — store it, you'll paste it into Opsgenie next.
Opsgenie → Settings → Integrations → Add integration → Webhook
Point the webhook at Landfall's trigger URL and add the secret as a custom header:
Webhook URL https://api.landfalls.ai/triggers/opsgenie Header name x-landfall-opsgenie-secret Header value The secret from the previous step
Opsgenie retries a non-2xx delivery with backoff and eventually disables the webhook outright. Landfall answers 202 to every authenticated delivery — including an action it doesn't act on — so an odd-but-authenticated payload doesn't turn into an infinite retry loop.
Reference
| Field | Value |
|---|---|
| API key (GenieKey) | Opsgenie API integration key, used for reads |
| Region | us (default) · eu |
| Trigger actions handled | Create → opens/attaches · Acknowledge/Close → recorded on the linked incident |
See Integrations architecture for how every Landfall integration shares this same connector shape, and today's actual agent-access status (Opsgenie's read connection isn't yet wired into the investigator agent's dynamic query surface, unlike AWS/Datadog/Coralogix/GitHub).