File content, represented as a stream of bytes. Note: As with all bytes fields, protobuffers use a pure binary representation, whereas JSON representations use base64.
Currently, this field only works for files.annotate requests. It does not work for files.asyncBatchAnnotate requests.
A base64-encoded string.
mimeType
string
The type of the file. Currently only "application/pdf", "image/tiff" and "image/gif" are supported. Wildcards are not supported.
[[["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-07-10 UTC."],[[["\u003cp\u003eThe \u003ccode\u003econtent\u003c/code\u003e field represents the file's content as a stream of bytes, encoded in base64 for JSON representation.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003emimeType\u003c/code\u003e field specifies the file type, with only "application/pdf", "image/tiff", and "image/gif" currently supported.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003econtent\u003c/code\u003e field is only applicable for \u003ccode\u003efiles.annotate\u003c/code\u003e requests and does not work for \u003ccode\u003efiles.asyncBatchAnnotate\u003c/code\u003e requests.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003econtent\u003c/code\u003e field requires a string in base64-encoded format, with a binary representation for protocol buffers.\u003c/p\u003e\n"]]],[],null,[]]
