There’s a typo in the OpenAPI spec for the “Request PDF Transcript” endpoint.
Current path:
/api/vi/omnichannel/{rid}/request-transcript
Expected path:
/api/v1/omnichannel/{rid}/request-transcript
The typo is also reflected in the generated operationId:
post-api-vi-omnichannel-rid-request-transcript
This appears to be an accidental vi → v1 mismatch in omnichannel.yaml around line 7201.
Because client SDKs and generated API bindings rely directly on the spec, this currently produces requests targeting a non-existent endpoint.
I can open a PR with the path and operationId correction if that’s the preferred workflow.
There’s a typo in the OpenAPI spec for the “Request PDF Transcript” endpoint.
Current path:
/api/vi/omnichannel/{rid}/request-transcriptExpected path:
/api/v1/omnichannel/{rid}/request-transcriptThe typo is also reflected in the generated
operationId:post-api-vi-omnichannel-rid-request-transcriptThis appears to be an accidental
vi→v1mismatch inomnichannel.yamlaround line 7201.Because client SDKs and generated API bindings rely directly on the spec, this currently produces requests targeting a non-existent endpoint.
I can open a PR with the path and
operationIdcorrection if that’s the preferred workflow.