Integration tasks
Create, test, and troubleshoot inbound alert integrations, and where the copied integration URLs get their hostname.
Start with the provider page in the integration catalog. After saving the integration, send a test event and verify service mapping, deduplication, urgency, and recovery behavior. If the request is rejected, use integration troubleshooting.
Where the copied URL comes from
On a service's Integrations tab, the webhook URL you copy for a provider, the Events API endpoint and the cURL sample all start with OpsKnight's Application URL, resolved in this order:
- Settings → System → App URL, when an administrator has saved one.
NEXT_PUBLIC_APP_URL.NEXTAUTH_URL.http://localhost:3000.
A trailing slash on the saved value is ignored, so the copied URL never contains //api.
Events API v2 integrations always post to <Application URL>/api/events; other providers post to
<Application URL>/api/integrations/<provider>?integrationId=…&integrationKey=….
Changed in 2.2.0. In 2.1.0 the service page built these URLs from
NEXT_PUBLIC_APP_URL(orNEXTAUTH_URL) only, so they could disagree with Settings → System → App URL. If you copied an integration URL in 2.1.0 and the two values differ, check the hostname configured in the provider. It still works only while that host is an allowed application host (see Application URL and host routing).
Last updated for v2.2.0
Edit this page on GitHub