Error causing post analysis data to be unavailable

Support Help
1

i get this error 2026-04-09 15:08:58.298 call_c519f5378e8e70e640c2718966d info: Ending call: call_c519f5378e8e70e640c2718966d

2026-04-09 15:08:58.299 call_c519f5378e8e70e640c2718966d info: Webhook triggered for transcript_updated

2026-04-09 15:08:58.688 call_c519f5378e8e70e640c2718966d info: Webhook retry 1 for transcript_updated

2026-04-09 15:08:59.080 call_c519f5378e8e70e640c2718966d info: Webhook retry 2 for transcript_updated

2026-04-09 15:08:59.714 call_c519f5378e8e70e640c2718966d error: Error triggering webhook for transcript_updated Axios Error: error code: ERR_BAD_REQUEST, error message: Request failed with status code 403
response status: 403
response data: [“user is not authorized”]2026-04-09 15:09:01.188 call_c519f5378e8e70e640c2718966d error: Error triggering webhook for call_ended Axios Error: error code: ERR_BAD_REQUEST, error message: Request failed with status code 403
response status: 403
response data: [“user is not authorized”]

2026-04-09 15:09:06.585 call_c519f5378e8e70e640c2718966d info: Webhook triggered for call_analyzed

2026-04-09 15:09:06.928 call_c519f5378e8e70e640c2718966d info: Webhook retry 1 for call_analyzed

2026-04-09 15:09:07.314 call_c519f5378e8e70e640c2718966d info: Webhook retry 2 for call_analyzed

2026-04-09 15:09:07.942 call_c519f5378e8e70e640c2718966d error: Error triggering webhook for call_analyzed Axios Error: error code: ERR_BAD_REQUEST, error message: Request failed with status code 403
response status: 403
response data: [“user is not authorized”] what the problem?

2

Hi @duncan

The error is not from Retell AI — it’s from your webhook server. Your server is returning a 403 Forbidden with "user is not authorized" when Retell tries to send webhook events (transcript_updated, call_ended, call_analyzed) to your endpoint.

Your webhook endpoint has authentication/authorization that is rejecting Retell’s requests.

Thank You

3

so you mean to say that the webhooks events were unauthorized?we haven’t changed our codebase what might have caused the issue because we only saw it in one incident