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

timestring

fromTimezonestring

toTimezonestring

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

Supports all IANA timezone identifiers and provides clear offset information for coordinating across multiple geographic locations.

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

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

View all integrations →

Other ways to use Meeting Time Converter

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

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

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. You pass valid source and target timezone names to calculate the difference between them.

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 requires a 24-hour time string in HH:MM format, such as 09:30 or 16:45. 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 40,000 credits, taking up one-fifth of the Starter plan's monthly allowance. At 2 credits per call, that works out to about $0.30 per 1,000 conversions. The Free plan includes 100 conversions each month.

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
`time`Required	string	`14:30`	Time in HH:MM format (24-hour) time
`fromTimezone`Required	string	`America/New_York`	Source IANA timezone identifier timezone
`toTimezone`Required	string	`Europe/London`	Target IANA timezone identifier timezone

Optional

Parameter	Type	Example	Description
`date`Optional	string	`2024-03-15`	Optional date in YYYY-MM-DD format (defaults to today) date

Example request

1
2

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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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.

Sample response

{
  "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 — 2 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	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

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.

Compare all pricing tiers →

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

1
2

curl "https://api.apiverve.com/v1/meetingtimeconverter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/meetingtimeconverter-apiSource, issues and the examples this page is built from.ReferenceMeeting Time Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/meetingtimeconverternpm APIVerve.API.MeetingTimeConverterNuGet

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.

Install — npm

npm install @apiverve/meetingtimeconverter

Node.js

const 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

npm@apiverve/meetingtimeconverterThe published Node.js client, versioned and signed.GitHubapiverve/meetingtimeconverter-apiSource, issues and the examples this page is built from.ReferenceMeeting Time Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.MeetingTimeConverterNuGet

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.

Python

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

@apiverve/meetingtimeconverternpm APIVerve.API.MeetingTimeConverterNuGet

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.

Install — NuGet

dotnet add package APIVerve.API.MeetingTimeConverter

C# / .NET

using 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

NuGetAPIVerve.API.MeetingTimeConverterThe published C# / .NET client, versioned and signed.GitHubapiverve/meetingtimeconverter-apiSource, issues and the examples this page is built from.ReferenceMeeting Time Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/meetingtimeconverternpm

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

@apiverve/meetingtimeconverternpm APIVerve.API.MeetingTimeConverterNuGet

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.

PHP

$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

@apiverve/meetingtimeconverternpm APIVerve.API.MeetingTimeConverterNuGet

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.

Ruby

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.body

Resources

Also published for

@apiverve/meetingtimeconverternpm APIVerve.API.MeetingTimeConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Conversion

View all 33 →

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

Meeting Time Converter API

Try it — live request, no key required

About the Meeting Time Converter API

What people use it for

Ways to call it

Other ways to use Meeting Time Converter

Questions.

Request parameters — GET /v1/meetingtimeconverter

Required

Optional

Authentication

Response — GET /v1/meetingtimeconverter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/meetingtimeconverter

Resources

Also published for

Call it from Node.js — GET /v1/meetingtimeconverter

Resources

Also published for

Call it from Python — GET /v1/meetingtimeconverter

Resources

Also published for

Call it from C# / .NET — GET /v1/meetingtimeconverter

Resources

Also published for

Call it from Go — GET /v1/meetingtimeconverter

Resources

Also published for

Call it from PHP — GET /v1/meetingtimeconverter

Resources

Also published for

Call it from Ruby — GET /v1/meetingtimeconverter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Meeting Time Converter API

Data Conversion

Related articles

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

Explore the catalog