Invalid Auth header in webhook


#1

I am seeing an invalid authorization header being sent back on my Webhook. It does work some of the time, but I’m getting the invalid header quite frequently.

A good header comes over as:

Basic <string>

The bad header comes over as just a string with no “Basic” prefix. Here is one example:

SDp38oyfTz-OTIFQoQLk4w

My webhook is a v2 webhook and I am listening for the following events: meeting_ended, recording_completed, and recording_transcript_completed.

Please advise.


#2

Hi Dayal,

This is a known issue and will be resolved in an upcoming release. The release is slated for this weekend. Let us know if you continue to see issues after this weekend.