The Sheets API’s value input option controls parsing. Choose it based on whether a field is literal data or intended spreadsheet input.
Understand the two modes
RAW stores supplied values without user-entry parsing. USER_ENTERED interprets them using rules similar to typing into the Sheets interface, so strings can become numbers, dates, or formulas.
Inspect the JSON value type too. A number already rounded by the sending program cannot be restored by choosing RAW afterward; identifiers should be preserved as strings throughout the transfer.
Match the mode to the field
For literal IDs, external descriptions, and text beginning with an equals sign, RAW string input avoids unintended user-entry interpretation. For a deliberately authored formula, USER_ENTERED can be appropriate after reviewing the expression and destination.
Date-like strings and decimal punctuation can depend on spreadsheet locale under user-entered parsing. Do not assume a string such as 03/04 has a universal calendar interpretation.
Read back and compare
Test leading-zero IDs, long digit strings, formula-like text, a genuine formula, and a known date. Read the resulting values using an appropriate render option and inspect formulas separately where needed.
Keep the write limited to an approved test range before changing production. Do not overwrite formulas or validation structures outside the intended cells. Document which fields are strings, numbers, or formulas and why each input mode was chosen. A successful HTTP response confirms the request was accepted; only a semantic readback shows whether Sheets stored and interpreted the values as intended for that workflow.
References
- ValueInputOption | Google Sheets | Google for Developers
- Set a spreadsheet’s location & calculation settings
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.