Skip to main content
Webhooks enable Risk Cloud to send real-time messages to your third-party tools. This article covers the webhook URL API use cases for managing those integrations. For an introduction to Risk Cloud Webhooks, see the Webhooks quick start.

Use cases

Get Webhook URLs

Requires BUILD role access.
Request body: none. Response body: an array of webhook URL objects.

Generate a new webhook secret

Requires ADMIN role access.
Request body: none. Response body: the new webhook URL secret.

Create Webhook URL

Requires ADMIN role access.
Response: 200 with an object of the same shape as the request, plus additional fields populated by Risk Cloud.

Update Webhook URL

Requires ADMIN role access.
Response: 200 with an object of the same shape as the request, plus additional fields populated by Risk Cloud.

FAQ

What do I use for Header Name and Header Value? Header Name is typically set to Authorization, and Header Value is typically set to Bearer <token>. How long does a webhook secret last? A webhook secret never expires unless it’s changed. Best practice is to rotate it every 6–12 months, but the cadence is up to your organization. What LogicGate IP addresses can I add to an internal allow list? LogicGate only provides dynamic IP addresses, not static ranges. If you need to allow list traffic, use an IaaS platform (Azure, Google Cloud, or AWS) to do so instead.