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

Lucky / Unlucky Directions

POST
/chinese/feng-shui/lucky-directions
request.sh
curl -X POST https://api.astroway.info/v1/chinese/feng-shui/lucky-directions \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "date": "1990-06-15", "gender": "male" }'

Personal 4 lucky + 4 unlucky compass directions from Kua. Standard Pa Kua mapping.

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

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
gender required
string
Allowed values: male female
solarYear
integer
>= 1800 <= 2200
language
string
Example
{
"date": "1990-06-15",
"gender": "male"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
kuaNumber
number
nullable
group
string
nullable
lucky
object
sheng_chi
object
direction
string
nullable
meaning
string
nullable
tian_yi
object
direction
string
nullable
meaning
string
nullable
nien_yen
object
direction
string
nullable
meaning
string
nullable
fu_wei
object
direction
string
nullable
meaning
string
nullable
unlucky
object
ho_hai
object
direction
string
nullable
meaning
string
nullable
wu_kuei
object
direction
string
nullable
meaning
string
nullable
liu_sha
object
direction
string
nullable
meaning
string
nullable
chueh_ming
object
direction
string
nullable
meaning
string
nullable
Example
{
"ok": true,
"data": {
"kuaNumber": 2,
"group": "West",
"lucky": {
"sheng_chi": {
"direction": "NE",
"meaning": "Wealth, success, opportunities: best for desks, headboards."
},
"tian_yi": {
"direction": "W",
"meaning": "Health, vitality, healing: good for bedrooms."
},
"nien_yen": {
"direction": "NW",
"meaning": "Love, family harmony: good for entrances."
},
"fu_wei": {
"direction": "SW",
"meaning": "Personal growth, peace: good for studies."
}
},
"unlucky": {
"ho_hai": {
"direction": "E",
"meaning": "Mishaps, minor accidents."
},
"wu_kuei": {
"direction": "SE",
"meaning": "Quarrels, gossip."
},
"liu_sha": {
"direction": "S",
"meaning": "Six killings: serious losses."
},
"chueh_ming": {
"direction": "N",
"meaning": "Total loss / endings: worst direction."
}
}
}
}

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