Import one ES module or use window.TimeNivoBrowserAPI. No API key is required; operations run locally with the browser’s time-zone database.
Quick start
Import the module
import { TimeNivoBrowserAPI } from '/assets/v10/js/browser-api.js';
const result = TimeNivoBrowserAPI.convert({
date: '2026-08-05',
time: '15:00',
from: 'Africa/Cairo',
to: ['Asia/Tokyo', 'Europe/London']
});
Every result includes engine metadata, the runtime time-zone source and whether the operation stayed local.
Surface
Available methods
currentTime(zone, at?)
Current local time, offset, DST state and next change.
convert(options)
Convert one wall time into one or more named zones.
timeDifference(options)
Offset difference between two zones at an instant.
dstTransitions(zone, options?)
Upcoming offset transitions with before/after values.
businessDays(options)
Count supplied business days with caller-provided holidays.
meetingScore(options)
Explain one candidate using the same fairness engine as the workspace.
bestMeetingSlots(options)
Rank slots and produce a four-week rotation.
batchConvert(options)
Convert one instant across a list of zones.
citySearch(query)
Search the bundled curated city catalog.
timezoneAtCoordinate(lat, lon)
Approximate nearest bundled reference city; not a boundary lookup.
Accuracy contract
What the Browser API does not claim
It does not ship a private time-zone database or guarantee that every browser has the same tzdb release. Coordinate lookup is explicitly approximate. Use the hosted coordinate endpoint where production boundary accuracy is required.