---
title: "Understanding Timezone Information Between the Validic Endpoint Usage and Time Support and Format Spreadsheets"
canonical: "https://help.validic.com/space/VCS/1635385484/Understanding%20Timezone%20Information%20Between%20the%20Validic%20Endpoint%20Usage%20and%20Time%20Support%20and%20Format%20Spreadsheets"
format: markdown
---
###### **This article pertains to:** [Legacy API (V1)] 

---

***Why is it that there are Apps that support the standard "utc_offset" field as illustrated on Validic's "Standard Endpoint Fields Used per App" while these Apps do not support timezone information as shown in the "Timezone Support and Format Spreadsheet"?***

The [Standard Endpoint Fields Used per App](https://validic.atlassian.net/wiki/spaces/VCS/pages/1681129566/Standard+Metrics+Used+per+App) spreadsheet illustrates what Apps populate certain standard field attributes such as "utc_offset". However, this does not mean that the App provides the end-user's exact timezone information. When an App does not support the timezone information of an end-user, Validic will return the default value for this standard field attribute of "+00:00".

The [Timestamp Timezone Support and Format](https://validic.atlassian.net/wiki/spaces/VCS/pages/1630372218/Timestamp+Timezone+Support+and+Format) spreadsheet specifically shows what Apps do support the exact timezone of the end-user and those that do not. Those that don't are labeled as "N" regardless of whether the App populates the "utc_offset" standard field.