POST/api/astro/eclipse/next-solar/1 credit

Next solar eclipse

The next solar eclipse anywhere on Earth, with every contact time named. The underlying engine returns ten datetimes in a positional array, where knowing that element 4 is the start of totality means reading source code. This returns them as named fields: begin, totality_begin, maximum, totality_end, end, and the centre-line times. Filter by eclipse_type (total, annular, partial, hybrid) and by centrality — whether the shadow's axis actually reaches the Earth's surface. Set direction to "before" to find the most recent one instead of the next. This is a GLOBAL search: it answers when, not whether you can see it. Use /api/astro/eclipse/local/ for that.

https://yogataraapi.prahlad.app/api/astro/eclipse/next-solar/

Test Request

Authentication

Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.

X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/json

Request fields

Field	Type	Required	Notes
date_time	string (date-time)	required	The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers.
centrality	string	optional	Central means the Moon's shadow axis actually touches the Earth. Only meaningful when eclipse_type is not 'any'. `anycentralnon-central`
direction	string	optional	Search forward from date_time, or backward. `afterbefore`
eclipse_type	string	optional	Restrict the search to one kind of solar eclipse. `anytotalannularpartialhybrid`
elevation	number (double)	optional
keys	array	optional	Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls.
latitude	number (double)	optional	Latitude of the place, in decimal degrees. Positive is north, negative is south. Example: 26.9124 for Jaipur, 40.7128 for New York. Minutes and seconds are not accepted - convert first.
longitude	number (double)	optional	Longitude of the place, in decimal degrees. Positive is east, negative is west. Example: 75.7873 for Jaipur, -74.0060 for New York. Note the sign: a missing minus puts New York in China.
timezone_as_float	number (double)	optional	UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30), -5 for New York in winter, 5.75 for Nepal. This is NOT validated against date_time - if the two disagree you get a successful response for the wrong moment, so derive both from the same source. Use the offset in force on that date, not today's: a summer birth in a country with daylight saving needs the summer offset. min -12 · max 14

Example request

curl -X POST https://yogataraapi.prahlad.app/api/astro/eclipse/next-solar/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date_time":"2026-01-01T00:00:00+00:00","timezone_as_float":0,"eclipse_type":"total","centrality":"any","direction":"after"}'

Response

{
  "data": {
    "found": true,
    "searched_from": "2026-01-01T00:00:00Z",
    "direction": "after",
    "eclipse": {
      "kind": "solar",
      "type": "total",
      "centrality": "central",
      "maximum": "2026-08-12T17:45:57Z",
      "times": {
        "maximum": "2026-08-12T17:45:57Z",
        "local_apparent_noon": "2026-08-12T17:03:51Z",
        "begin": "2026-08-12T15:34:30Z",
        "end": "2026-08-12T19:57:57Z",
        "totality_begin": "2026-08-12T16:58:05Z",
        "totality_end": "2026-08-12T18:34:00Z",
        "centre_line_begin": "2026-08-12T17:00:06Z",
        "centre_line_end": "2026-08-12T18:32:01Z"
      }
    }
  },
  "status": 200,
  "is_error": false,
  "message": "successful"
}

Captured from a real call using the exact request above. Results sit under data.

Errors

Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.