Skip to content
Occult API
POST/api/astro/eclipse/next-lunar/1 credit

Next lunar eclipse

The next lunar eclipse, with the penumbral, partial and total phases named. Worth using rather than reading the raw array: swisseph's lunar timing array is NOT in the order a reader would guess. Element 1 is unused, elements 2 and 3 are the partial phase and 6 and 7 are the penumbral phase, so a naive left-to-right reading mislabels the whole timeline. These fields are named from the engine's verified index map.

https://yogataraapi.prahlad.app/api/astro/eclipse/next-lunar/
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

FieldTypeRequiredNotes
date_timestring (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.

directionstringoptional

Search forward from date_time, or backward.

afterbefore
elevationnumber (double)optional
keysarrayoptional

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.

latitudenumber (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.

longitudenumber (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_floatnumber (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-lunar/ \
  -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,"direction":"after"}'

Response

{
  "data": {
    "found": true,
    "searched_from": "2026-01-01T00:00:00Z",
    "direction": "after",
    "eclipse": {
      "kind": "lunar",
      "type": "total",
      "centrality": null,
      "maximum": "2026-03-03T11:33:42Z",
      "times": {
        "maximum": "2026-03-03T11:33:42Z",
        "partial_begin": "2026-03-03T09:50:06Z",
        "partial_end": "2026-03-03T13:17:18Z",
        "totality_begin": "2026-03-03T11:04:34Z",
        "totality_end": "2026-03-03T12:02:51Z",
        "penumbral_begin": "2026-03-03T08:44:25Z",
        "penumbral_end": "2026-03-03T14:23:08Z"
      }
    }
  },
  "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.