When you create a web hook, the web hook acts as a notification system for events in Greenhouse Recruiting delivering a payload about the event to the configured endpoint.
Web hook log
The web hook log tracks activity for each web hook configured in your organization's Greenhouse Recruiting account, allowing you to audit successful web hook activity as well as web hook errors.
To review the web hook log, click the Configure icon on your navigation bar then select Dev Center on the left.
Click Web Hooks.
Click Web Hook Log on the next page.
The web hook log will detail each web hook's activity, including the endpoint URL, the secret key used, the response received, and the date and time of the activity.
Troubleshoot a web hook error
Use the chart below to troubleshoot web hook responses:
||The web hook successfully delivered its payload to the endpoint!|
||The web hook was unauthenticated or unauthorized. This typically indicates the Secret Key used in configuring your webhook isn't being accepted by the endpoint. Reach out to the partner application or developer who owns the endpoint to confirm that the secret key is correct, and if needed, edit your web hook to update the secret key.|
||The web hook was forbidden from the server. This means the endpoint is not accepting payloads from Greenhouse Recruiting. Reach out to the partner application or developer who owns the endpoint to troubleshoot further.|
||The endpoint doesn't exist or can't be found. Reach out to the partner application or developer who owns the endpoint, and if necessary, edit your web hook to update the receiving endpoint.|
||The endpoint server is down or can't be found. This error typically resolves within some time, but if the issue persists, reach out to the partner application or developer who owns the endpoint to troubleshoot further.|
||The endpoint is not available to receive the web hook payload. Reach out to the partner application or developer who owns the endpoint to troubleshoot further.|
When you create a new web hook, you can configure an email address to receive error notifications.
To update the email used for error notifications, edit the web hook.