Opsgenie
Collect on-call schedules, escalation policies, and team-membership evidence as read-only compliance signal through the Opsgenie REST API. Signl4 is primarily a webhook-receiver product with no meaningful read API; capture Signl4 alerting evidence via the generic comms-alerting-webhook template instead of a bespoke connector.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Read-only API inventory endpoint checks
- Evidence assets generated through the generic HTTP connector
Endpoints this template queries
The exact Opsgenie API endpoints called once connected. All read-only GET requests unless noted.
- GET/schedules
- GET/escalations
- GET/teams
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.opsgenie.com/v2)
- Endpoints (JSON)(prefilled: [ { "id": "schedules", "name": "On-call schedules", "path": "/schedules" }, { "id": "escalations", "name": "Escalation policies", "path": "/escalations" }, { "id": "teams", "name": "Teams", "path": "/teams" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Opsgenie evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Opsgenie evidence
Get a guided demo, or start by scanning any domain for free.