Build global apps without location friction.
Timezone, holiday, and geolocation APIs for world-ready products that work everywhere.
Use cases
GET /v1/places/timezone
Local check-in and reminders that match property time
Align schedules with local timezones. Reduce confusion for travelers and distributed teams.
Example
A vacation rental stores each property in an IANA timezone. Confirmation emails and SMS use server-side conversion so โ4pm check-inโ always means local wall clock.
GET /v1/places/geocode
Turn addresses into pins dispatch can route to
Convert addresses to coordinates instantly. Speed up maps, delivery, and search.
Example
Dispatch receives โ123 Main St, Austin.โ Geocode returns lat/lng and normalized address; the driver app routes to the pin instead of ambiguous city center.
GET /v1/places/postal/{code}
Block bad postal codes before labels print
Validate postal codes for global shipping. Catch bad addresses before they leave the warehouse.
Example
Checkout validates postal format against the selected country before label purchase. German 5-digit PLZ mismatches block the order with a field-level error instead of a return label.
GET /v1/places/holidays
Ship and support when each market is actually open
Avoid holidays in every market with date rules. Ship confidently across regions.
Example
Release automation checks holidays for DE, BR, and JP. Deployments that would land on a public holiday are pushed to the next business day with a Slack summary for PMs.
GET /v1/places/working-days
SLA dates that respect regional weekends and holidays
Calculate working days across countries. HR and ops stop spreadsheet gymnastics.
Example
HRIS computes case SLA due dates excluding weekends and country-specific holidays for each employeeโs site. Reps get the same number in the UI and in the exported audit log.
GET /v1/places/time/{timezone}
Market clocks that survive DST without hotfixes
Show accurate clocks for every city. Build trust in trading, support, and scheduling UIs.
Example
A trading dashboard footer calls world-time for New York, London, and Tokyo venue codes. DST changes track automatically; engineers do not ship emergency hotfixes twice a year.
Reliability at a glance
APIS you can trust.
99.99%
Platform uptime target
~500ms
Average API response time
250+
Countries & regions in data products
How it works
Three short steps from picking a pattern to measuring impact in your own metrics.
Pick a pattern that sounds familiar
Choose a card that mirrors where logistics or calendars hurt you (timezones, addresses, or launch windows). Each outcome maps to endpoints that bake in regional rules.
Wire it into your stack
Use the reference examples, add your API key, and call the HTTPS endpoints from your backend or edge. Most teams ship the first version the same week they read the docs.
Prove it with your own metrics
Compare before and after in dashboards you already trust: fewer failures, shorter queues, calmer support, or faster pages once bad inputs stop propagating.
Wire endpoints for this division
Use the cards above for scenarios; request shapes, parameters, examples, and errors are in the technical directory for this category.
Industries we serve
Build world-ready apps today.
Integrate in minutes. Make every location feel local.