Webhooks
Summary
Flxpoint webhooks send an HTTPS POST to a URL you configure whenever a subscribed event occurs, optionally scoped to a single source or channel, so your systems can react to events like a fulfillment request entering processing.
A Flxpoint webhook sends an event to one of your services over HTTPS POST, so that system can act when something happens in Flxpoint (for example, a fulfillment request entering processing). Webhooks can be scoped to a specific source or channel, or left on for all.
- Event-driven — fires on a subscribed event you choose.
- HTTPS POST — event data is sent to your URL via HTTPS.
- Source/channel scope — limit to one source or channel, or leave on for all.
- Built to be resilient — handle events idempotently and asynchronously.
- Click the settings gear in the bottom left of your screen.
- Click Webhooks.
- Click Add Webhook in the top right.
- Fill in the required information (fields below).
- Click Save.
Set up the webhook with the following fields:
| Field | Detail |
|---|---|
| Name | A label for the webhook. |
| URL | The HTTPS endpoint that receives the event via POST. |
| Notification Email | Where notifications about the webhook go. |
| Subscribed Event | The event that triggers the POST to your URL. |
| Source / Channel (optional) | If the event relates to the chosen source or channel, its info is shared; leave blank for all. |
| Practice | Why |
|---|---|
| Make processing idempotent | The same event can arrive more than once; handling it twice should be safe. |
| Process asynchronously | Queue incoming events so your endpoint responds quickly and does not time out. |
| Receive over HTTPS | The endpoint must accept HTTPS POST requests. |
The webhook is not being received. Confirm the URL is HTTPS and publicly reachable, that it accepts POST, and that the Subscribed Event and any source/channel scope actually match the events you expect.
A firewall is blocking Flxpoint's calls. If you need to allowlist Flxpoint by IP, contact Support to confirm the current outbound details rather than assuming a fixed range — do not hard-code an IP that may change.
The same event fires more than once. This is expected behavior for webhooks. Make your event handling idempotent (for example, dedupe on the event identifier) so repeats are harmless.
What is a webhook used for? To notify another one of your systems when an event happens in Flxpoint, so it can act — for example, when a fulfillment request enters processing.
How do I create one? Go to the Settings gear (bottom left) → Webhooks → Add Webhook. Set Name, URL, Notification Email, and Subscribed Event, optionally choose a source/channel, then Save.
Can I limit a webhook to one source or channel? Yes — select the source or channel during setup. Leave both blank to receive the event for all.
Can a webhook fire when an invoice is created? Yes, if there is a subscribed event for it — choose that event when creating the webhook so your endpoint receives the payload.
Does Flxpoint send from a fixed IP I can allowlist? Contact Support to confirm current outbound details before allowlisting; avoid hard-coding an address that may change.