Permissions: Basic and above who can manage and configure webhooks

Product tier: Available for all subscription tiers

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.

In some cases, you may see errors in the web hook log or in error notifications configured for the webhook. This article can help you understand and troubleshoot these errors.

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 Configure icon icon on your navigation bar then select Dev Center on the left.

Configure page showing Dev Center highlighted in marigold emphasis box

Click Web Hooks.

Dev Center page shows a marigold emphasis box around Web Hooks button

Click Web Hook Log on the next page.

The Dev center page shows Web Hook Log button highlighted in a marigold emphasis box

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.

Web hook log shows an example entry with fake endpoint and fake secret key and a 202  OK  response from December 13 at 438pm

Note: The date and time shown are according to your personal Greenhouse Recruiting account settings.

Troubleshoot a web hook error

Use the chart below to troubleshoot web hook responses:

Response Solution
200 (OK) The web hook successfully delivered its payload to the endpoint!
401 (Unauthorized) 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.
403 (Forbidden) 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.
404 (Not found) 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.
500 (Internal server error) 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.
503 (Unavailable) 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.

Error notifications

When you create a new web hook, you can configure an email address to receive error notifications.

Edit an example web hook shows configuration settings

To update the email used for error notifications, edit the web hook.