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
No key required to try it. Get a key to use it in your app.
{
"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
- GraphQL
- Query language
- 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.
Which timezone identifiers does the converter accept?
Can I convert meeting times for specific future dates?
Does the response include the calculated time difference?
What time format does the conversion require?
What would 20,000 meeting conversions a month cost me?
Request parameters — GET /v1/meetingtimeconverter
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
timeRequired | string | 14:30 | Time in HH:MM or HH:MM:SS format (24-hour) time |
fromTimezoneRequired | string | America/New_York | Source timezone: an IANA name (America/New_York), a North American abbreviation (EST, EDT, PST, PDT and so on, always DST-aware) or a UTC/GMT offset such as UTC+05:30 timezone |
toTimezoneRequired | string | Europe/London | Target timezone, in the same forms as fromTimezone timezone |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
dateOptional | string | 2024-03-15 | Optional date in YYYY-MM-DD format (defaults to today) date |
curl "https://api.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon&date=2024-03-15" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/meetingtimeconverter
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
originalTime | string | "14:30" | Original time in source timezone |
convertedTime | string | "19:30:00" | Converted time in target timezone |
date | string | "2026-09-18" | The meeting date the conversion was performed for (YYYY-MM-DD), defaulting to today in UTC |
fromTimezone | string | "America/New_York" | Source timezone identifier |
toTimezone | string | "Europe/London" | Target timezone identifier |
timeDifference | number | 5 | Time difference between zones |
fromOffset | string | "-04:00" | The source timezone's UTC offset on that date, as +HH:MM or -HH:MM |
toOffset | string | "+01:00" | The target timezone's UTC offset on that date, as +HH:MM or -HH:MM |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 1 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Meeting Time Converter calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 200 | Free |
| Starter | $29.99 | 200,000 | 200,000 | $0.15 |
| Pro | $99.99 | 1,000,000 | 1,000,000 | $0.10 |
| Mega | $299.99 | 4,000,000 | 4,000,000 | $0.07 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/meetingtimeconverter
No SDK to install — this is a plain HTTPS call to /v1/meetingtimeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/meetingtimeconverter" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/meetingtimeconverter
Install the Node.js SDK, then call the Meeting Time Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/meetingtimeconverterconst res = await fetch("https://api.apiverve.com/v1/meetingtimeconverter", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/meetingtimeconverter
No SDK to install — this is a plain HTTPS call to /v1/meetingtimeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/meetingtimeconverter",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/meetingtimeconverter
Install the C# / .NET SDK, then call the Meeting Time Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.MeetingTimeConverterusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/meetingtimeconverter");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/meetingtimeconverter
No SDK to install — this is a plain HTTPS call to /v1/meetingtimeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/meetingtimeconverter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/meetingtimeconverter
No SDK to install — this is a plain HTTPS call to /v1/meetingtimeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/meetingtimeconverter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/meetingtimeconverter
No SDK to install — this is a plain HTTPS call to /v1/meetingtimeconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/meetingtimeconverter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Meeting Time Converter form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Meeting Time Converter API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Meeting Time Converter API.
Data Conversion
- ASCII85 Encoder
- Base64 Encoder/Decoder
- Color Converter
- CSV to JSON Converter
- File Size Formatter
- HTML Entities Encoder/Decoder
- HTML to Image
- JSON to CSV Converter
- JSON to JSONP
- JWT Decoder
- Markdown Table Generator
- Markdown to HTML
- Markdown to Image
- Markdown to PDF
- Math Calculator
- Meeting Time Converter
- Number Base Converter
- Number to Words
- Placeholder Text Generator
- Punycode Converter
- Query String Builder
- Relative Time Formatter
- Roman Numeral Converter
- Text to Color
- Unicode Escape/Unescape
- Unit Converter
- Unix Timestamp Converter
- URL Encoder/Decoder
- URL to Markdown
- Variable Name Converter
- Website to Text
- Words to Numbers
- XML to JSON
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read
Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read