NewAPIVerve Academy: free courses and certifications anyone can verify.Explore the Academy →

Meeting Time Converter API

GET

Schedule global meetings without manual timezone math.

Meeting Time Converter transforms meeting times between any two timezones, calculating time differences and UTC offsets for global coordination.

Try it — live request, no key required

Request
GETapi.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon
Query parameters
Verification
Format

No key required to try it. Get a key to use it in your app.

Example
{
  "status": "ok",
  "error": null,
  "data": {
    "originalTime": "14:30",
    "convertedTime": "19:30:00",
    "date": "2026-09-18",
    "fromTimezone": "America/New_York",
    "toTimezone": "Europe/London",
    "timeDifference": 5,
    "fromOffset": "-04:00",
    "toOffset": "+01:00"
  }
}

About the Meeting Time Converter API

Meeting Time Converter tells you what a meeting time in one city is in another. Send a 24-hour time, a source timezone and a target timezone, and optionally the meeting date, and get back the converted time, the hour difference between the two zones and each zone's UTC offset. It supports all IANA timezone identifiers and works as a time zone converter and time difference calculator for any two zones, for example Eastern (EST) to Pacific (PST) or New York to London.

Scheduling tools, calendar invites, team handbooks and booking pages use it to show attendees their local time without carrying their own timezone tables. Passing the actual meeting date matters: daylight saving starts and ends on different dates in different countries, and the gap between two cities can change by an hour for a few weeks a year.

The Free plan and paid plans return the same fields.

How it works

The API treats time as a wall-clock time in fromTimezone on date. It first reads the date and time as if they were UTC, then looks up the UTC offset of each zone for that moment using the runtime's IANA timezone data. Subtracting the source offset gives the real instant, which is then formatted in toTimezone as convertedTime in 24-hour HH:MM:SS form.

date is optional and defaults to today's date in UTC. It matters because offsets follow daylight saving rules: on a summer date America/New_York reports -04:00 and on a winter date -05:00. fromOffset and toOffset are those offsets as +HH:MM or -HH:MM, and timeDifference is the target offset minus the source offset in hours, so it can be fractional for zones such as Asia/Kolkata (+5.5) and negative when the target is behind.

convertedTime carries no date, so a conversion that crosses midnight does not say whether the result falls on the previous or next day; compare timeDifference with the input time to work that out. Each timezone is validated on its own, and a name the runtime does not recognise returns a 400 that says which parameter was wrong. A date and time that do not form a valid moment also return a 400. Offsets are looked up at the input reading as UTC, so within a few hours of a daylight saving change the result can be off by an hour.

What people use it for

Global Scheduling
Schedule international meetings by converting times across timezones
Calendar Apps
Display meeting times in user's local timezone automatically
Conference Planning
Coordinate multi-timezone events and conference calls
Travel Planning
Convert appointment times when traveling across timezones

Without writing code

Worldwide Timezone Widgets for Windows shows the hours that suit every city at once.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON
Default REST response
XML
Markup format
YAML
Human-readable
CSV
Tabular export
Beta
GraphQL
Query language
New
MCP
For AI agents

Other ways to use Meeting Time Converter

Same data, same APIVerve account, same credit balance — one key works on all of them.

Questions.

Common questions about the Meeting Time Converter API.

Read the docs →
Which timezone identifiers does the converter accept?
It supports all standard IANA timezone identifiers, including regional names like America/New_York and Europe/London. The North American abbreviations EST/EDT, CST/CDT, MST/MDT, PST/PDT, AKST/AKDT and HST map to their city zone, so EST in July correctly reads as daylight time, and fixed offsets such as GMT+1 or UTC+05:30 are accepted too.
Can I convert meeting times for specific future dates?
Yes. You can pass an optional date formatted as YYYY-MM-DD to evaluate a meeting on that calendar day. When the date parameter is omitted, the calculation defaults to the current day.
Does the response include the calculated time difference?
Yes. Along with the converted time, the response provides the original time, both timezone identifiers, and the exact time difference between the two locations.
What time format does the conversion require?
The time parameter takes a 24-hour time string in HH:MM or HH:MM:SS format, such as 09:30 or 16:45:00. Standard 12-hour formats using AM or PM markers are not accepted.
What would 20,000 meeting conversions a month cost me?
That volume uses 20,000 credits, taking up a tenth of the Starter plan's monthly allowance. At 1 credit per call, that works out to about $0.15 per 1,000 conversions. The Free plan includes 200 conversions each month.

Ready to build with Meeting Time Converter? Start with 200 free credits — one key unlocks all 404+ APIs.

Explore the catalog

404+ APIs on the same key and the same response shape.

Browse all APIs