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

Stream Eclipse Incoming

POST
/stream/eclipse-incoming
request.sh
curl -X POST https://api.astroway.info/v1/stream/eclipse-incoming \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{}'

Countdown to next 5 eclipses.

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

This endpoint reads nothing from the request body. Send {} (or any object, which is ignored).

object
Example
{}

Successful calculation

Media type application/json
object
ok
boolean
data
object
timestamp
string
nullable
count
number
nullable
eclipses
Array<object>
nullable
object
kind
string
nullable
type
string
nullable
longitude
number
nullable
sign
string
nullable
maxAt
string
nullable
beginAt
string
nullable
endAt
string
nullable
daysUntil
number
nullable
hoursUntil
number
nullable
nextEventAt
string
nullable
tickSeconds
number
nullable
transport
string
nullable
sseUpgrade
string
nullable
pricing
string
nullable
Example
{
"ok": true,
"data": {
"timestamp": "2026-08-23T22:05:26.964Z",
"count": 5,
"eclipses": [
{
"kind": "lunar",
"type": "partial",
"longitude": 334.8525422076384,
"sign": "Pisces",
"maxAt": "2026-08-28T04:12:58.339Z",
"beginAt": "2026-08-28T02:33:53.071Z",
"endAt": "2026-08-28T05:52:03.261Z",
"daysUntil": 4.26,
"hoursUntil": 102.1
}
],
"nextEventAt": "2026-08-28T04:12:58.339Z",
"tickSeconds": 3600,
"transport": "http-polling",
"sseUpgrade": "Use the same endpoint with /sse subpath for Server-Sent Events (planned).",
"pricing": "10 credits/call (Tier 1): each tick recomputes positions, so it is a live compute, not a cheap lookup. Poll on the returned `tickSeconds`; see docs/PRICING.md §11."
}
}

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