Webhooks
Setup and management
Please refer to this article for instructions on webhook setup on the idibu account. Webhooks can also be managed via the REST API.
Payload URL - the URL where the webhook events will be sent.
Content type - define the format of the webhooks sent. It's either JSON or x-www-form-urlencoded.
Secret - non-required parameter you can add to authenticate your own requests. You can append it with SSL verification.
Content sent - You can either have all events sent to the provided URL or you can choose from the following:
- Vacancy - triggers whenever a Vacancy is created or updated.
- Search - triggers whenever a Talent Pool search is run.
- Candidate - Triggers whenever a Candidates is received or updated.
- Users - Triggers whenever a given User of your account logs in.
- Post - Triggers whenever an Advert is sent.
Processing webhook responses
Your endpoint must acknowledge having received the data by sending a 200 OK response. Any response outside the 200 range will indicate that your system did not receive the event.
If there is no successful response within 5 seconds, idibu will resend the event up to a total of 19 times over the next 48 hours (with the timeout period gradually increasing) - then the event will ultimately fail.
To ensure your app doesn't exceed the timeout limit, we recommend processing the data after responding with the successful receipt first.