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

Long Count

POST
/mayan/long-count
request.sh
curl -X POST https://api.astroway.info/v1/mayan/long-count \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "date": "1990-06-15" }'

Five-place positional notation: baktun.katun.tun.uinal.kin. Days since 4 Ahau 8 Cumku (3114 BC).

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}$/
Example
{
"date": "1990-06-15"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
longCount
object
baktun
number
nullable
katun
number
nullable
tun
number
nullable
uinal
number
nullable
kin
number
nullable
notation
string
nullable
daysSinceCreation
number
nullable
Example
{
"ok": true,
"data": {
"longCount": {
"baktun": 12,
"katun": 18,
"tun": 17,
"uinal": 2,
"kin": 15,
"notation": "12.18.17.2.15",
"daysSinceCreation": 1853895
}
}
}

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