I changed my global webhook URL (Settings → Webhooks) from a Pipedream URL to webhook.site for testing. The dashboard shows the new URL is saved correctly.
However:
Detail Logs show webhooks still failing with 401 [“Unauthorized”]
webhook.site shows ZERO incoming requests
webhook.site has no authentication - it accepts everything
This means Retell is not sending to the URL shown in my settings. It appears to be caching my old webhook URL.
Details:
Workspace: Taskiva Workspace
Current webhook URL in settings: webhook.site (test URL)
Call ID examples: call_2e23acd5c238b6bf56d95d4c79a, call_9ec587fe277c9021780ced27d48
Based on a similar issue documented in the community, the 401 “Unauthorized” error you’re seeing suggests Retell is still sending requests to your old webhook URL, not the new one displayed in your dashboard settings(1).
When this issue occurred previously, the resolution involved verifying that the webhook URL in the settings matched what was actually being used(1). The support team identified that “the old one is in the settings, not the new one” and recommended updating it and ensuring “the phone number is using the correct version”(1).
Steps to resolve:
Verify the webhook URL is saved correctly - Double-check that your webhook.site URL is properly saved in Settings → Webhooks(1)
Check agent version - If you’re using phone numbers with inbound webhooks, ensure the phone number is bound to the correct agent version that has the updated webhook URL(1)
Publish/update your agent - After changing the webhook URL, make sure to publish or update your agent configuration(2)
Test with a new call - Make a fresh test call after confirming the settings are correct(2)
The webhook system sends a POST request to your endpoint with a 10-second timeout(3). If no success status (2xx) is received within 10 seconds, the webhook will retry up to 3 times(3).
If the issue persists after verifying these settings, you may need to contact Retell support directly with your agent ID and call IDs for further investigation(1).