Incode Webhooks
Overview of webhooks that let you send requests from the Incode platform backend to your API
What are webhooks?
Webhooks are an asynchronous notification mechanism. They let you send requests from the Incode backend to your API. They are sometimes called "reverse APIs." You can use webhooks to inform your application of different events that happen in the Incode platform.
What webhooks are available?
- Onboarding status webhook - This webhook triggers every time the status changes for an Onboarding Session.
- INE scraping webhook - (Deprecated) Provides the INE Scraping results asynchronously.
- Videoselfie upload webhook - Notifies you when the video selfie recording file becomes available
- Global watchlists webhook - Triggered when a global watchlist result is updated.
- Work history webhook - Triggered after processing the work history search for a user.
- Proof of payment webhook - Triggered after processing the payment proof validation for a user.
Configuring your webhooks
You can configure the webhooks behavior by navigating on the dashboard to Configuration -> Webhooks.
Configuring webhooks destination
You can configure the URL that you wish to use for every webhook. A single URL per webhook is allowed
Each webhook will be sent to only one destinationIf you need the webhook on different endpoints in your system, you will have to receive it in a single endpoint and broadcast within your infrastructure
Configuring webhooks custom headers
In the same screen, you can also configure custom headers which you might want to include for your system to receive.
Custom headers are sent on every webhook request made to your system, and they are static (you can't include dynamic values).
Retry Policy
Webhook retries will be triggered in the following scenarios:
- Timeout when calling your endpoint.
- The returned status code from your service is not
200 OKalong with theapplication/jsonheader or the status code204 No content.
The retry policy for webhooks is exponential with an initial interval of 30s, multiplier of 2.5, and max attempts of 5:
| Retry attempt | Delay (seconds) | Delay (minutes) | Total (minutes) |
|---|---|---|---|
| 1 | 30 | 0.50 | 0.5 |
| 2 | 75 | 1.25 | 1.75 |
| 3 | 187.5 | 3.13 | 4.88 |
| 4 | 468.75 | 7.81 | 12.69 |
| 5 | 1,171.88 | 19.53 | 32.22 |
This means the maximum time a webhook can take to reach its destination is approximately 32 minutes.
Whitelisting webhook source IPs
If you need to whitelist IPs to allow inbound traffic into your network, please add the following IP addresses:
US Environment
- SAAS (production):
| IP | Active |
|---|---|
54.86.34.156 | Currently Active |
3.142.125.52 | Currently Active |
54.85.117.182 | Starting February 2, 2026 |
3.233.40.153 | Starting February 2, 2026 |
DEMO (development) Environment
- Since October 2024,
34.198.171.165(previously18.210.119.234).
EU Environment
- SAAS EU (production and demo): IP
18.158.116.18
Updated 2 days ago