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

Yearly Forecast

POST
/bazi/yearly
request.sh
curl -X POST https://api.astroway.info/v1/bazi/yearly \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "natalDate": "1990-05-15", "targetYear": 2027 }'

Compares target year pillar against natal day master + natal year branch. Returns element-flow relation (companion / mother / output / control / wealth) per Sheng-Ke cycle, branch clashes (六冲), and trine support (三合).

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
natalDate required
string
/^\d{4}-\d{2}-\d{2}$/
natalTime
string
/^\d{2}:\d{2}(:\d{2})?$/
natalTzOffset
number
>= -14 <= 14
targetYear required
integer
>= 1900 <= 2100
language
string
Example
{
"natalDate": "1990-05-15",
"targetYear": 2027
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
natalDayMaster
object
stem
string
nullable
element
string
nullable
yin
boolean
nullable
targetYear
number
nullable
targetPillar
object
stem
string
nullable
branch
string
nullable
pillar
string
nullable
animal
string
nullable
elementFlow
object
stem
object
element
string
nullable
relation
string
nullable
flavor
string
nullable
branch
object
element
string
nullable
relation
string
nullable
flavor
string
nullable
branchInteractions
object
clashes
Array
nullable
trineSupport
Array
nullable
notes
Array<string>
nullable
disclaimer
string
nullable
Example
{
"ok": true,
"data": {
"natalDayMaster": {
"stem": "Geng",
"element": "Metal",
"yin": false
},
"targetYear": 2027,
"targetPillar": {
"stem": "Ding",
"branch": "Wei",
"pillar": "Ding-Wei",
"animal": "Goat"
},
"elementFlow": {
"stem": {
"element": "Fire",
"relation": "control",
"flavor": "control / officer (官杀): pressure or authority year"
},
"branch": {
"element": "Earth",
"relation": "mother",
"flavor": "mother / supporting (印): nurturing year"
}
},
"branchInteractions": {
"clashes": [],
"trineSupport": []
},
"notes": [
"Element flow uses the standard 五行生克 (Sheng-Ke) cycle relative to natal day master."
],
"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"
}
}
Корисно?