Webhook callback URLs

Webhook callback URLs are used by some applications to send events to IBM® App Connect. Callback URLs are registered automatically for some connectors, while for others, you register them manually.

A webhook is an HTTP request that some applications use to send notifications of when events occur. Event notifications are sent to a callback URL that identifies the endpoint. In this case, the endpoint is an event connector in an IBM App Connect flow. For example, Eventbrite uses webhooks to notify App Connect when events occur for some objects, such as attendees, events, and orders.

Automatic webhook registration

For some connectors, such as Eventbrite, the App Connect URL is registered automatically. The application uses this URL to publish events, which then trigger the flow in App Connect. For example, if you add an Eventbrite New attendee event to your flow, Eventbrite uses the webhook callback URL to trigger the flow when a new attendee is added to your event.
Screenshot shows an Eventbrite New attendee event in the flow editor. A webhook callback URL is provided automatically.
The webhook registration is removed from Eventbrite in the following circumstances:
  • You stop a running flow in App Connect Designer
  • You undeploy or deactivate a flow
  • You delete the integration runtime where the flow is deployed

Manual webhook registration

For some connectors, such as IBM Maximo®, you must register the webhook manually.
Screenshot shows an IBM Maximo New asset event in the flow editor. The description of the Webhook callback URL field instructs you to register the webhook URL on Maximo.

You can find the webhook callback URL by adding an event to a flow and connecting to your account. To copy the URL to your clipboard, click The icon that represents copy to clipboard.. You can then work with the account administrator to register the webhook with the application.

Note: A webhook URL is associated with an account. Therefore, all flows that use that account have the same webhook URL and are triggered when an event occurs.