Actual
Tomorrow
The date 01/29/2026 is months in the past, yet the API returns "Tomorrow". The relative text appears to be cached from when the date was first inserted, not recalculated relative to the API call time.
Comparison with UI export
Exporting the same document as HTML from the Quip UI (File → Export → HTML) returns the correct actual date in the same tag. Same element ID, different text content.
Impact
It is impossible to programmatically extract accurate dates from Quip documents via the API when cells use date mentions.
Request
Either:
- Return actual dates in the html field (like the UI export does), or
- Provide an API parameter to disable relative date rendering, or
- Include raw date values as a data attribute on the element (e.g. data-date="2026-01-29")
Actual
Tomorrow
The date 01/29/2026 is months in the past, yet the API returns "Tomorrow". The relative text appears to be cached from when the date was first inserted, not recalculated relative to the API call time.
Comparison with UI export
Exporting the same document as HTML from the Quip UI (File → Export → HTML) returns the correct actual date in the same tag. Same element ID, different text content.
Impact
It is impossible to programmatically extract accurate dates from Quip documents via the API when cells use date mentions.
Request
Either: