Stream Sunrise/Sunset

POST

/stream/sunrise-sunset

request.sh

curl -X POST https://api.astroway.info/v1/stream/sunrise-sunset \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "latitude": 50.45, "longitude": 30.52, "timezoneOffset": 3 }'

▸ Спробувати POST /stream/sunrise-sunset

• Production

Today + tomorrow sun events.

Authorizations

• ApiKeyAuth

Parameters

Query Parameters

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

Request Body ^required

Media type application/json

object

latitude required

number

nullable

longitude required

number

nullable

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.

number

0 nullable >= -14 <= 14

Example

{
  "latitude": 50.45,
  "longitude": 30.52,
  "timezoneOffset": 3
}

Responses

200

Successful calculation

Media type application/json

object

ok

boolean

data

object

timestamp

string

nullable

today

object

date

string

nullable

sunrise

string

nullable

sunset

string

nullable

polarState

string

nullable

warning

nullable

tomorrow

object

date

string

nullable

sunrise

string

nullable

sunset

string

nullable

polarState

string

nullable

nextEventAt

string

nullable

nextEventKind

string

nullable

tickSeconds

number

nullable

transport

string

nullable

sseUpgrade

string

nullable

pricing

string

nullable

Example

{
  "ok": true,
  "data": {
    "timestamp": "2026-08-23T22:05:27.563Z",
    "today": {
      "date": "2026-08-23",
      "sunrise": "2026-08-23T02:58:18.342Z",
      "sunset": "2026-08-23T17:01:51.208Z",
      "polarState": "normal",
      "warning": null
    },
    "tomorrow": {
      "date": "2026-08-24",
      "sunrise": "2026-08-24T02:59:49.545Z",
      "sunset": "2026-08-24T16:59:47.969Z",
      "polarState": "normal"
    },
    "nextEventAt": "2026-08-24T02:59:49.545Z",
    "nextEventKind": "sunrise",
    "tickSeconds": 1800,
    "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."
  }
}

400

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"
      }
    ]
  }
}

401

Missing or invalid API key

Media type application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_API_KEY",
    "message": "Invalid API key"
  }
}