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

Via Combusta Check

POST
/horary/via-combusta
request.sh
curl -X POST https://api.astroway.info/v1/horary/via-combusta \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "moonLongitude": 200.5 }'

Check if the Moon or ASC is in the Via Combusta (15° Libra – 15° Scorpio), a classical prohibition in horary.

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
moonLongitude required
number
nullable
Example
{
"moonLongitude": 200.5
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
moonViaCombusta
boolean
nullable
moonLongitude
number
nullable
moonSign
string
nullable
ascViaCombusta
boolean
nullable
ascLongitude
number
nullable
warning
nullable
Example
{
"ok": true,
"data": {
"moonViaCombusta": false,
"moonLongitude": 75.4,
"moonSign": "Gemini",
"ascViaCombusta": false,
"ascLongitude": 180.5,
"warning": null
}
}

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?