The audio data bytes encoded as specified in the request, including the
header for encodings that are wrapped in containers (e.g. MP3, OGG_OPUS).
For LINEAR16 audio, we include the WAV header. Note: as
with all bytes fields, protobuffers use a pure binary representation,
whereas JSON representations use base64.
The audio data bytes encoded as specified in the request, including the
header for encodings that are wrapped in containers (e.g. MP3, OGG_OPUS).
For LINEAR16 audio, we include the WAV header. Note: as
with all bytes fields, protobuffers use a pure binary representation,
whereas JSON representations use base64.
The audio data bytes encoded as specified in the request, including the
header for encodings that are wrapped in containers (e.g. MP3, OGG_OPUS).
For LINEAR16 audio, we include the WAV header. Note: as
with all bytes fields, protobuffers use a pure binary representation,
whereas JSON representations use base64.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]