Meeting Time Converter API GET

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
Verification
Format

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

200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    // Meeting Time Converter response payload
  }
}

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
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
What does the Meeting Time Converter API do?
Meeting Time Converter transforms meeting times between any two timezones, calculating time differences and UTC offsets for global coordination.
How do I authenticate Meeting Time Converter API requests?
Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.
How much does the Meeting Time Converter API cost?
Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.
How fast is the Meeting Time Converter API?
Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.
What response formats does the Meeting Time Converter API support?
JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.
What HTTP method does the Meeting Time Converter API use?
GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

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

Explore the catalog

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

Browse all APIs