When I send 2025-12-31T10:00:00+09:00 through the API (Workflow → Call API to mutateTables), the table shows 19:00 (JST)—a 9-hour shift as if the value was saved as UTC. However, if I copy/paste the same value in the Data Editor, the cell displays 10:00 as expected. It looks like the parsing behavio…

[image] Big Tables - date/time column offset issue Ask for Help Well, that response you got from Support is not what I would have expected, so I just did a bit of testing. I created a new table and added some rows via the API, using curl from a terminal. Here …

Thanks for running those tests and sharing the screenshots — super helpful. To clarify my environment: I’m using a regular Glide Table (not a Big Table), and I’m writing via API v1 (POST ``https://api.glideapp.io/api/function/mutateTables) triggered from a Workflow → Call API action. The target col…

Your questions would only be correctly answered by a Glide engineer. As a fellow user, I would say what about sending the time at UTC+0 instead of trying to represent the current Japan time?

Time zone parsing for Date/Time via API differs from pasting in the Data Editor

Ask for Help

ThinhDinh August 21, 2025, 1:19am 2

Here’s the leg work @Darren_Murphy did a while ago.

Topic		Replies	Views
Mismatching date time between API and Glide tables Ask for Help	3	26	July 25, 2024
Big Tables - date/time column offset issue Ask for Help big-tables	15	196	January 23, 2025
Strange Date/Time behavior Ask for Help api , date-math	11	58	November 1, 2024
🆕 "Respect time zone" support for Date & Time column in Glide Tables & Airtable Community Resources	17	1899	September 24, 2025
Fix TimeZone issues writing to Google Calendar Ask for Help	8	71	December 9, 2025

Time zone parsing for Date/Time via API differs from pasting in the Data Editor

Related topics