POSThttps://yogataraapi.prahlad.app/api/astro/eclipse/upcoming/

Upcoming eclipses

Request bodyJSON

Paste an API key above to send.

Code snippet

curl -X POST https://yogataraapi.prahlad.app/api/astro/eclipse/upcoming/ \
  -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,"count":6,"kind":"both","direction":"after"}'

The next several eclipses, solar and lunar merged into one chronological list. One call and one credit instead of stepping the date forward yourself and paying for each single lookup, which is what building an eclipse calendar otherwise costs. Ask for up to 24, filter to solar or lunar only, or set direction to "before" to walk backwards through history.

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.
count	integer	optional	How many eclipses to return, at most 24. min 1 · max 24
direction	string	optional	Search forward from date_time, or backward. `afterbefore`
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.
kind	string	optional	`bothsolarlunar`
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

Full reference for this endpoint