Overview
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.
Live Test Meeting Time Converter API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
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_here"const res = await fetch('https://api.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon&date=2024-03-15', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon&date=2024-03-15",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon&date=2024-03-15", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
timeRequired | string | Time in HH:MM or HH:MM:SS format (24-hour) time |
fromTimezoneRequired | string | 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 | Target timezone, in the same forms as fromTimezone timezone |
dateOptional | string | Optional date in YYYY-MM-DD format (defaults to today) date |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- 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
Other ways to use Meeting Time Converter
Set up Meeting Time Converter on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Data Conversion: