When you create a webhook, the webhook 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 webhook log or in error notifications configured for the webhook. This article can help you understand and troubleshoot these errors.
Web hook log
The webhook log tracks activity for each webhook configured in your organization's Greenhouse Recruiting account, allowing you to audit successful webhook activity as well as webhook errors.
To access the webhook log, you'll need to navigate to the Webhooks page in the Dev Center.(Configure > Dev Center > Webhooks)
Once you're on the Webhooks page, click Webhook Log.
The webhook log page contains a list of the requests that were sent from your organization. You can use this page to filter for certain requests using the fields at the top of the page.
Note: The date and time shown are according to your personal Greenhouse Recruiting account settings.
Troubleshoot a webhook error
Use the chart below to troubleshoot webhook responses:
| Response | Solution |
200 (OK) |
The webhook successfully delivered its payload to the endpoint. |
401 (Unauthorized) |
The webhook was unauthenticated or unauthorized. This error 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 webhook to update the secret key. |
403 (Forbidden) |
The webhook was forbidden from the server. This error 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 webhook 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 webhook payload. Reach out to the partner application or developer who owns the endpoint to troubleshoot further. |
Error notifications
When you create a new webhook, you can configure an email address to receive error notifications.
To update the email used for error notifications, edit the webhook.