GET /maps/api/timezone/json

The Time Zone API provides a simple interface to request the time zone for locations on the surface of the earth, as well as the time offset from UTC for each of those locations. You request the time zone information for a specific latitude/longitude pair and date. The API returns the name of that time zone, the time offset from UTC, and the daylight savings offset.

Servers

https://www.googleapis.com
https://maps.googleapis.com
https://roads.googleapis.com

Query parameters

Name Type Required Description

Name	Type	Required	Description
`timestamp`	String	No	(Required) The desired time as seconds since midnight, January 1, 1970 UTC. The Time Zone API uses the `timestamp` to determine whether or not Daylight Savings should be applied, based on the time zone of the `location`. Note that the API does not take historical time zones into account. That is, if you specify a past timestamp, the API does not take into account the possibility that the location was previously in a different time zone.
`location`	String	No	(Required) A comma-separated latitude,longitude tuple, `location=39.6034810,-119.6822510`, representing the location to look up.
`language`	String	No	The language in which to return results. See the list of supported languages. Google often updates the supported languages, so this list may not be exhaustive. If `language` is not supplied, the API attempts to use the preferred language as specified in the `Accept-Language` header. The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component. If a name is not available in the preferred language, the API uses the closest match. The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.

timestamp

String

(Required) The desired time as seconds since midnight, January 1, 1970 UTC. The Time Zone API uses the timestamp to determine whether or not Daylight Savings should be applied, based on the time zone of the location.

Note that the API does not take historical time zones into account. That is, if you specify a past timestamp, the API does not take into account the possibility that the location was previously in a different time zone.

location

String

(Required) A comma-separated latitude,longitude tuple, location=39.6034810,-119.6822510, representing the location to look up.

language

String

The language in which to return results.

See the list of supported languages. Google often updates the supported languages, so this list may not be exhaustive.
If language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.
The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component.
If a name is not available in the preferred language, the API uses the closest match.
The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.