Timezone API
Getting started
Subscribe, copy your secret key, and resolve your first timezone.
The Syndaq Timezone API resolves IANA timezone ID, UTC offset, and abbreviation for any public IP—plus country and city when available.
v1 scope: timezone and related location fields for a public IP. Private and reserved addresses are rejected.
What you need
- A Timezone plan from the Syndaq API catalog.
- A secret key (
tz_sec_) from the Syndaq client area after your order is provisioned.
Timezone lookups are server-side only. Send your secret key from your backend or trusted worker. Do not embed it in client-side code, mobile apps, or public repositories.
Base URL
All Timezone endpoints are served from:
https://api.syndaq.com/v1/timezone/
Quick start
Replace tz_sec_YOUR_SECRET_KEY with the secret shown in Services for your Timezone subscription.
curl -sS "https://api.syndaq.com/v1/timezone/lookup/8.8.8.8" \
-H "Authorization: Bearer tz_sec_YOUR_SECRET_KEY"
You can also pass the IP as a query parameter:
curl -sS "https://api.syndaq.com/v1/timezone/lookup?ip=8.8.8.8" \
-H "Authorization: Bearer tz_sec_YOUR_SECRET_KEY"
A successful response includes timezone.id, timezone.utc_offset, timezone.abbreviation, and optional country/city fields.
How lookups work
| Step | What happens |
|---|---|
| 1 | Authenticate with your secret key. |
| 2 | Send a public IPv4 or IPv6 address. |
| 3 | Receive JSON with timezone fields (including a cached flag when Syndaq already holds a recent result). |
Private, reserved, and invalid addresses return a clear error and are not billed.
Manage your subscription
Sign in to the Syndaq client area and open Services. Select your Timezone service to:
- View usage and remaining monthly quota
- Copy or rotate your secret key
- Configure optional IP allowlists for API access
Next steps
- Authentication and limits: keys, rate limits, quotas, and IP restrictions
- API reference: endpoints, response fields, and error codes