# Time zone parsing for Date/Time via API differs from pasting in the Data Editor **URL:** https://community.glideapps.com/t/time-zone-parsing-for-date-time-via-api-differs-from-pasting-in-the-data-editor/83920 **Category:** Ask for Help **Tags:** api **Created:** [August 20, 2025, 2:46am UTC](https://community.glideapps.com/t/time-zone-parsing-for-date-time-via-api-differs-from-pasting-in-the-data-editor/83920 "2025-08-20T02:46:01Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh) #### Post date: [August 21, 2025, 1:19am UTC](https://community.glideapps.com/t/time-zone-parsing-for-date-time-via-api-differs-from-pasting-in-the-data-editor/83920/2 "2025-08-21T01:19:50Z")
> [@Big Tables - date/time column offset issue](https://community.glideapps.com/t/big-tables-date-time-column-offset-issue/75513/11): > > 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 are the results: (NB: this was with a regular table. See further below for results with a Big Table.) In the above: The first column is a date/time column with respect time zone enable The second column is a date/time column with respect time zone not enabled … Here’s the leg work @Darren_Murphy did a while ago. --- _[View the full topic](https://community.glideapps.com/t/time-zone-parsing-for-date-time-via-api-differs-from-pasting-in-the-data-editor/83920)._