FAQ.
common questions about the World Time API. click any question to expand.
›is the api free to use?
yes, up to 20,000 requests per month. beyond that you'll need a commercial plan.›how accurate is the time data?
highly accurate — sourced from industry-standard time servers, typically within milliseconds of true time.›what timezone formats are supported?
IANA Time Zone Database identifiers, e.g.America/New_York,Europe/London. you can list all supported timezones via/timezone.›can i use this api for commercial projects?
yes. personal and commercial use are both fine. exceed the free tier and you'll need a paid plan.›how do i handle daylight saving time?
DST is handled automatically. thedstfield shows whether DST is currently active;dst_fromanddst_untilmark the boundaries. see the schema page for details.›what happens if i request an invalid timezone?
the api returns a 404 error with a JSON body explaining that the timezone was not found.›is there a rate limit?
no. you can hit the api as fast as you like, up to your plan's monthly request quota.›can i get historical time data?
no — current time only. no historical queries, no future predictions beyond standard timezone rules.›how is my ip address used?
when you call/ipor/geo, the IP is used solely to derive the timezone or geolocation for the response. IP addresses are not stored.›what if the api is down?
the api is built for high availability on top-tier infrastructure. if anything goes wrong, updates are posted to the GitHub repo.›can i contribute to the project?
yes — the project is the first commercial time api that's also openly available on GitHub. licensed under BSL 1.1, which restricts production use unless explicitly granted. see the repo for full license details.›how do i report bugs or issues?
open an issue on the GitHub repo, or contact us if it's urgent.›what are the different support tiers?
tier B = low priority, tier A = medium, tier S = high. tier comes with the paid plan you choose. we may ask for your RapidAPI account ID to verify.