topic Re: List of all possible timezones (for query param) which meetings api needs (Meeting Library) in APIs & Integrations

List of all possible timezones (for query param) which meetings api needs (Meeting Library)

Ahassansm — Sat, 01 Nov 2025 21:10:18 GMT

So I am making an app in which I need to get all the timezone's and make no mistake. so Is this possible. I could use "IANA timezone database list", but in doubt if all of those are accepted.

Re: List of all possible timezones (for query param) which meetings api needs (Meeting Library)

GRajput — Mon, 03 Nov 2025 14:26:25 GMT

Hi @Ahassansm

While working with the HubSpot Meetings API, the time zones must be provided in a predefined format, typically similar to IANA time zone identifiers. However, not every IANA identifier is supported, since HubSpot only accepts the time zones available in its system. One advice I will give is to always test time zone via the Meetings API to make sure it’s accepted, and then use it in your code.

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.

Thanks!

Re: List of all possible timezones (for query param) which meetings api needs (Meeting Library)

DilshadShaikh — Mon, 03 Nov 2025 15:09:36 GMT

Greetings @Ahassansm,

Meeting Library API uses standard TZ identifiers (also known as IANA timezone database format) for the timezone query parameter.

According to the Library Meetings API guide, timezone values must use standard TZ identifiers such as:

America/New_York
Europe/Dublin

The documentation doesn't provide a complete list, but references the standard TZ database time zones (also called IANA TZDB format). You can find the full list of valid timezone identifiers at that Wikipedia link, which includes all standard IANA timezone names.

Here's the complete list of timezones that hubspot gives while creating the meeting, these time zones are accepted by HubSpot. So if you have doubt about the TZ database timezones, you can map it with these ones below:

UTC -08:00 Pacific Time
UTC -07:00 Mountain Time
UTC -06:00 Central Time
UTC -05:00 Eastern Time

Europe

UTC +00:00 Dublin, London, Lisbon
UTC +01:00 (Europe) Central European Time
UTC +02:00 Eastern European Time
UTC +02:00 Chisinau, Tiraspol
UTC +02:00 Kaliningrad
UTC +03:00 Istanbul, Kirov, Minsk, Moscow
UTC +04:00 Astrakhan, Samara, Saratov, Ulyanovsk

Canada

UTC -08:00 Pacific
UTC -07:00 Mountain
UTC -07:00 Yukon
UTC -06:00 Central
UTC -06:00 Saskatchewan
UTC -05:00 Eastern
UTC -04:00 Atlantic Time
UTC -03:30 Newfoundland

Africa

UTC +00:00 Greenwich Mean Time
UTC +01:00 (Africa) Central European Time
UTC +01:00 Casablanca, El Aaiun
UTC +01:00 Ceuta
UTC +02:00 South Africa Time
UTC +02:00 Cairo
UTC +03:00 East Africa Time

America

UTC -10:00 Adak, Atka
UTC -09:00 Anchorage, Juneau, Metlakatla, Nome
UTC -08:00 Pacific Time
UTC -07:00 Mountain Time
UTC -07:00 Arizona & Yukon Time
UTC -06:00 Central Standard Time
UTC -06:00 Central Time
UTC -05:00 Jamaica, Panama, Colombia
UTC -05:00 Eastern Time
UTC -05:00 Havana
UTC -04:00 Eastern Caribbean Time
UTC -04:00 Glace Bay, Goose Bay, Halifax, Moncton
UTC -03:00 Argentina, Brazil
UTC -03:00 Miquelon
UTC -03:00 Santiago
UTC -03:30 St Johns
UTC -02:00 Godthab, Nuuk, Scoresbysund
UTC -02:00 Noronha
UTC +00:00 Danmarkshavn

Antarctica

UTC -03:00 Palmer, Rothera
UTC +00:00 Troll
UTC +03:00 Syowa
UTC +05:00 Mawson, Vostok
UTC +07:00 Davis
UTC +08:00 Casey
UTC +10:00 DumontDUrville
UTC +11:00 Macquarie
UTC +13:00 McMurdo, South Pole

Arctic

UTC +01:00 Longyearbyen

Asia

UTC +02:00 Beirut
UTC +02:00 Famagusta, Nicosia
UTC +02:00 Gaza, Hebron
UTC +02:00 Jerusalem, Tel Aviv
UTC +03:00 Baghdad, Bahrain, Istanbul, Qatar
UTC +03:30 Tehran
UTC +04:00 Baku, Dubai, Muscat, Tbilisi
UTC +04:30 Kabul
UTC +04:00 Yerevan
UTC +05:00 Almaty, Aqtau, Aqtobe, Ashgabat
UTC +05:30 New Delhi, Mumbai, Calcutta
UTC +05:45 Kathmandu, Katmandu
UTC +06:00 Bishkek, Dacca, Dhaka, Kashgar
UTC +06:30 Rangoon, Yangon
UTC +07:00 Indochina Time
UTC +08:00 China, Hong Kong, Singapore
UTC +09:00 Seoul, Tokyo
UTC +10:00 Ust-Nera, Vladivostok
UTC +11:00 Magadan, Sakhalin, Srednekolymsk
UTC +12:00 Anadyr, Kamchatka

Atlantic

UTC -04:00 Bermuda
UTC -03:00 Stanley
UTC -02:00 South Georgia
UTC -01:00 Azores
UTC -01:00 Cape Verde
UTC +00:00 Canary, Faeroe, Faroe, Madeira
UTC +00:00 Reykjavik, St Helena
UTC +01:00 Jan Mayen

Australia

UTC +08:45 Eucla
UTC +08:00 Perth, West
UTC +09:30 Darwin, North
UTC +10:30 Adelaide, Broken Hill, South, Yancowinna
UTC +10:00 Brisbane, Lindeman, Queensland
UTC +11:00 Australian Eastern Time
UTC +11:00 LHI, Lord Howe

Brazil

UTC -05:00 Acre
UTC -04:00 West
UTC -03:00 East
UTC -02:00 DeNoronha

Chile

UTC -05:00 EasterIsland
UTC -03:00 Continental

Indian

UTC +03:00 Antananarivo, Comoro, Mayotte
UTC +04:00 Mahe, Mauritius, Reunion
UTC +05:00 Kerguelen, Maldives
UTC +06:00 Chagos
UTC +06:30 Cocos
UTC +07:00 Christmas

Mexico

UTC -08:00 BajaNorte
UTC -07:00 BajaSur
UTC -06:00 General

Pacific

UTC -11:00 Midway, Niue, Pago Pago, Samoa
UTC -10:00 Honolulu, Johnston, Rarotonga, Tahiti
UTC -09:00 Gambier
UTC -09:30 Marquesas
UTC -08:00 Pitcairn
UTC -06:00 Galapagos
UTC -05:00 Easter
UTC +09:00 Palau
UTC +10:00 Chuuk, Guam, Port Moresby, Saipan
UTC +11:00 Bougainville, Efate, Guadalcanal, Kosrae
UTC +12:00 Fiji, Funafuti, Kwajalein, Majuro
UTC +12:00 Norfolk
UTC +13:00 Apia, Enderbury, Fakaofo, Kanton
UTC +13:00 Auckland
UTC +13:45 Chatham
UTC +14:00 Kiritimati

Hope this helps, if it does then help the community by marking it as a solution.

Happy HubSpotting.

Thanks & Regards,
Dilshad Shaikh

Re: List of all possible timezones (for query param) which meetings api needs (Meeting Library)

RubenBurdin — Fri, 07 Nov 2025 23:00:44 GMT

Hi @Ahassansm

You’re on the right track. The Meetings Library endpoints expect the timezone query param in IANA format (e.g., America/New_York, Europe/Dublin).

HubSpot doesn’t publish its own master list; instead it follows the IANA identifiers, as shown directly in the Meetings API guide where the examples pass ?timezone=America/New_York for availability and booking (https://developers.hubspot.com/docs/api-reference/library-meetings-v3/guide )

Practical way to avoid mistakes: keep the canonical IANA set in your app (from tzdb/moment-timezone or your language’s standard lib), then validate before calling HubSpot. If the user selects a city alias that isn’t in IANA, normalize it to a valid region name.

I also recommend a tiny health check on startup that pings one known link with a few representative zones to guard against regressions. One small clarifier: do you need the exhaustive list for a UI picker, or only to validate inputs coming from elsewhere? That will change whether you ship the full tzdb or a curated subset.

If your app later needs meeting data synced back to other systems with consistent local times, Stacksync keeps HubSpot and your source aligned in two-way sync so timestamps and statuses stay consistent without manual patches.