Skip to content
AstroWay/api v2.254.12 · docs
all systems operational

Planetary Hours

POST
/planetary-hours
request.sh
curl -X POST https://api.astroway.info/v1/planetary-hours \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "date": "2026-06-21", "latitude": 50.45, "longitude": 30.52, "timezoneOffset": 3, "atLocalHour": 15.2 }'

Chaldean planetary hours for a date and place: 12 from sunrise to sunset and 12 from sunset to sunrise, so an hour is rarely 60 minutes. startHour and endHour are decimal local hours. Send atLocalHour (decimal local time, e.g. 15.2 for 15:12) to have the hour containing it marked isCurrent; without it no hour carries the field, because the answer is cacheable and a flag from the server clock would be stale by the time it renders. sunTimes.polarState is normal, polar-day or polar-night, and in the two polar cases there is nothing to divide, so hours comes back empty with a warning saying why.

fields
string

Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.

Example
planets.name,planets.longitude
precision
integer
<= 15

Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.

Example
4
Media type application/json
object
date required
string
/^\d{4}-\d{2}-\d{2}$/
latitude required
number
nullable
longitude required
number
nullable
timezoneOffset

Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

number
0 nullable >= -14 <= 14
timezone

IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.

string
atLocalHour

Local time of day in decimal hours, e.g. 15.2 for 15:12. When sent, the hour containing it carries isCurrent: true and every other hour carries false. When omitted, no hour carries the field at all: it is not false, it is unasked.

number
<= 24
Example
{
"date": "2026-06-21",
"latitude": 50.45,
"longitude": 30.52,
"timezoneOffset": 3,
"atLocalHour": 15.2
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
date
string
nullable
latitude
number
nullable
longitude
number
nullable
timezone
number
nullable
sunTimes
object
riseJD
number
nullable
setJD
number
nullable
riseHour
number
nullable
setHour
number
nullable
polarState
string
nullable
dayRulerPlanetId
number
nullable
dayRulerPlanetName
string
nullable
dayOfWeek
number
nullable
hours
Array<object>
nullable
object
number
number
nullable
planetId
number
nullable
planetName
string
nullable
startHour
number
nullable
endHour
number
nullable
isDaytime
boolean
nullable
isCurrent
boolean
nullable
Example
{
"ok": true,
"data": {
"date": "2026-06-21",
"latitude": 50.45,
"longitude": 30.52,
"timezone": 3,
"sunTimes": {
"riseJD": 2461212.573777389,
"setJD": 2461213.2591750845,
"riseHour": 4.770657330751419,
"setHour": 21.220202028751373,
"polarState": "normal"
},
"dayRulerPlanetId": 0,
"dayRulerPlanetName": "Sun",
"dayOfWeek": 0,
"hours": [
{
"number": 1,
"planetId": 0,
"planetName": "Sun",
"startHour": 4.770657330751419,
"endHour": 6.141452722251415,
"isDaytime": true,
"isCurrent": false
},
{
"number": 8,
"planetId": 0,
"planetName": "Sun",
"startHour": 14.366225071251392,
"endHour": 15.737020462751389,
"isDaytime": true,
"isCurrent": true
}
]
}
}

Validation error

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_INPUT",
"message": "Validation failed: date: Date must be YYYY-MM-DD",
"details": [
{
"path": "date",
"message": "Date must be YYYY-MM-DD"
}
]
}
}

Missing or invalid API key

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_API_KEY",
"message": "Invalid API key"
}
}
Was this helpful?