Skip to content

Horoscope Timezone Helper

Use this helper to fetch accepted IANA timezone IDs before calling relative-day report routes (today, yesterday, tomorrow).

It prevents date-shift mistakes across regions and ensures users in different geographies resolve the correct local day.

Endpoint

Method Path
GET https://api.numerologyapi.com/api/v1/horoscope/timezones

Auth

Provide your API key header:

  • X-API-Key: YOUR_API_KEY

Request Parameters

This endpoint does not require query or body parameters.

Example Request

curl --request GET \
  --url "https://api.numerologyapi.com/api/v1/horoscope/timezones" \
  --header "X-API-Key: YOUR_API_KEY"

Example Response

{
  "count": 596,
  "timezones": [
    "Africa/Abidjan",
    "Africa/Accra",
    "Africa/Addis_Ababa"
  ]
}

Response Fields

Field Type Description
count integer Total number of accepted timezone IDs returned.
timezones array[string] Supported IANA timezone names.

Integration Workflow

  1. Call /api/v1/horoscope/timezones once and cache the list in your backend/client.
  2. Validate the user-selected timezone against that list.
  3. Send the validated timezone in daily report requests.

Example daily request with timezone:

curl --request POST \
  --url "https://api.numerologyapi.com/api/v1/horoscope/reports/today?lang=en" \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "sign": "TAURUS",
  "timezone": "America/New_York",
  "sections": ["general"]
}'

Notes

  • Use valid IANA format (for example: America/New_York, Africa/Douala, Asia/Tokyo).
  • Avoid abbreviations like EST, PST, or GMT+1.
  • count can vary slightly by environment/tzdata version.