Following a recent update to our API specification and documentation, an unexpected cascading impact affected the callback request body for transcription jobs.
While we initially believed the issue had been fully resolved yesterday evening, we’ve since identified that some callbacks continued to fail for certain requests.
Impact period (Europe/Paris time):
During these windows, transcriptions were correctly processed, but the corresponding callbacks were not delivered.
Our team is now resending all impacted callbacks to ensure you receive the expected results.
Importantly, this callback issue only affected customers still using the deprecated callback_url parameter, and did not impact requests using the new callback_config format.
We’ve already identified part of the root cause and are actively monitoring the system to guarantee a permanent fix.
We sincerely apologize for the inconvenience this may have caused and deeply appreciate your patience and understanding as we work to fully stabilize the service.