Meeting Time ConverterMeeting Time Converter API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 582ms|p50: 544ms|p75: 608ms|p90: 684ms|p99: 838ms

Overview

To use Meeting Time Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

URL
https://api.apiverve.com/v1/meetingtimeconverter

Example

How to call the Meeting Time Converter API in different programming languages.

cURL Request
curl -X GET \
  "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"
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon&date=2024-03-15', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/meetingtimeconverter?time=14%3A30&fromTimezone=America%2FNew_York&toTimezone=Europe%2FLondon&date=2024-03-15', headers=headers)

data = response.json()
print(data)
Go (net/http)
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")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Example Response
{
  "status": "ok",
  "error": null,
  "data": {
    "originalTime": "14:30",
    "convertedTime": "14:30:00",
    "fromTimezone": "America/New_York",
    "toTimezone": "Europe/London",
    "timeDifference": 5,
    "fromOffset": "-05:00",
    "toOffset": "+00:00"
  }
}

Authentication

The Meeting Time Converter API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Meeting Time Converter API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Meeting Time Converter API:

Convert Meeting Time

ParameterTypeRequiredDescriptionDefaultExample
timestringrequired
Time in HH:MM format (24-hour)
Format: time (e.g., 14:30)
-14:30
fromTimezonestringrequired
Source IANA timezone identifier
Format: timezone (e.g., America/New_York)
-America/New_York
toTimezonestringrequired
Target IANA timezone identifier
Format: timezone (e.g., Europe/London)
-Europe/London
datestringoptional
Optional date in YYYY-MM-DD format (defaults to today)
Format: date (e.g., 2024-03-15)
-2024-03-15

Response

The Meeting Time Converter API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <originalTime>14:30</originalTime>
    <convertedTime>14:30:00</convertedTime>
    <fromTimezone>America/New_York</fromTimezone>
    <toTimezone>Europe/London</toTimezone>
    <timeDifference>5</timeDifference>
    <fromOffset>-05:00</fromOffset>
    <toOffset>+00:00</toOffset>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  originalTime: '14:30'
  convertedTime: '14:30:00'
  fromTimezone: America/New_York
  toTimezone: Europe/London
  timeDifference: 5
  fromOffset: '-05:00'
  toOffset: '+00:00'
CSV Response
200 OK
keyvalue
originalTime14:30
convertedTime14:30:00
fromTimezoneAmerica/New_York
toTimezoneEurope/London
timeDifference5
fromOffset-05:00
toOffset+00:00

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

FieldTypeSample ValueDescription
originalTimestring"14:30"
-
convertedTimestring"14:30:00"
-
fromTimezonestring"America/New_York"
-
toTimezonestring"Europe/London"
-
timeDifferencenumber5
-
fromOffsetstring"-05:00"
-
toOffsetstring"+00:00"
-

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Meeting Time Converter through GraphQL to combine it with other API calls in a single request. Query only the meeting time converter data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Meeting Time Converter in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  meetingtimeconverter(
    input: {
      time: "14:30"
      fromTimezone: "America/New_York"
      toTimezone: "Europe/London"
      date: "2024-03-15"
    }
  ) {
    originalTime
    convertedTime
    fromTimezone
    toTimezone
    timeDifference
    fromOffset
    toOffset
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Meeting Time Converter API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Meeting Time Converter requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Meeting Time Converter API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Meeting Time Converter

Official Meeting Time Converter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Meeting Time Converter works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Frequently Asked Questions

How do I get an API key for Meeting Time Converter?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Meeting Time Converter and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Meeting Time Converter cost?

Each successful Meeting Time Converter API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful meeting time converter lookups.

Can I use Meeting Time Converter in production?

The free plan is for testing and development only. For production use of Meeting Time Converter, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Meeting Time Converter from a browser?
Yes! The Meeting Time Converter API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Meeting Time Converter credit limit?

When you reach your monthly credit limit, Meeting Time Converter API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?