curl -X POST https://yogataraapi.prahlad.app/api/astro/sunrise/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"2026-09-01T06:00:00+05:30","timezone_as_float":5.5,"latitude":26.9124,"longitude":75.7873}'Sunrise and sunset for a date and place, with the length of the day in seconds. For the moon, use /api/astro/moonrise/. Send a date, a latitude, a longitude and the UTC offset. Nothing else. The same figures are reachable through /api/astro/celestial/, but only if you know to ask for the SUN by name, to put the rising-convention switch first in the keys array, and to read element zero of a two-element array whose second element is a ten-float ephemeris tuple. This uses Hindu rising - upper limb, no refraction - the same convention /api/astro/panchanga/ builds its day from, so sunset minus sunrise here equals that endpoint's day_length to the second. The sunset returned is always the one that follows the sunrise. Either field can be null: inside a polar day or night the sun does not rise or set, and null says so. /api/astro/celestial/ returns "2000-11-24T12:00:00Z" for that case, which is julian day zero rather than an instant. One boundary to know: this answers for the CIVIL day you named, while the panchanga day runs sunrise to sunrise. Ask for a moment before sunrise and panchanga is still describing the previous day, so its day_length will differ from the interval here. Both are correct for their own question.
| 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. |
| latitude | number (double) | required | 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. min -89.9 · max 89.9 |
| longitude | number (double) | required | 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. min -180 · max 180 |
| timezone_as_float | number (double) | required | 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 |
| 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. |