Перейти до вмісту
AstroWay/api v2.200.11 · docs
усі системи в нормі

Day Master

POST
/bazi/day-master
request.sh
curl -X POST https://api.astroway.info/v1/bazi/day-master \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "date": "1990-05-15", "time": "15:30:00", "timezone": "Europe/Kyiv" }'

Day stem element + yin/yang polarity + canonical archetype description. The “self” character in BaZi from which all other pillars are interpreted.

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}$/
time
string
/^\d{2}:\d{2}(:\d{2})?$/
timezoneOffset

Ignored when timezone is sent.

number
>= -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
language
string
Example
{
"date": "1990-05-15",
"time": "15:30:00",
"timezone": "Europe/Kyiv"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
dayMaster
object
stem
string
nullable
element
string
nullable
yin
boolean
nullable
polarityName
string
nullable
dayPillar
object
stem
string
nullable
branch
string
nullable
pillar
string
nullable
animal
string
nullable
stemElement
string
nullable
branchElement
string
nullable
yin
boolean
nullable
interpretation
object
summary
string
nullable
archetype
string
nullable
notes
Array<string>
nullable
disclaimer
string
nullable
Example
{
"ok": true,
"data": {
"dayMaster": {
"stem": "Geng",
"element": "Metal",
"yin": false,
"polarityName": "Yang Metal"
},
"dayPillar": {
"stem": "Geng",
"branch": "Chen",
"pillar": "Geng-Chen",
"animal": "Dragon",
"stemElement": "Metal",
"branchElement": "Earth",
"yin": false
},
"interpretation": {
"summary": "Yang Metal day master: Geng.",
"archetype": "Geng (Yang Metal): sword / iron; decisive, direct, strong-willed."
},
"notes": [
"Day master is the day stem: the core \"self\" character in BaZi. All other pillars relate to it."
],
"disclaimer": "BaZi pillars use the canonical 60-jiazi cycle, anchored at 1990-01-01 = Bing-Yin. Year and month boundaries are the exact Lichun and 節 instants from the ephemeris, stated in China Standard Time; pass time and timezoneOffset for births near a boundary. Day and hour follow the birthplace clock, with the day rolling at 23:00 local."
}
}

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"
}
}
Корисно?