POSThttps://yogataraapi.prahlad.app/api/astro/monthly_panchang/

Monthly panchang

Request bodyJSON

Paste an API key above to send.

Code snippet

curl -X POST https://yogataraapi.prahlad.app/api/astro/monthly_panchang/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"latitude":26.9124,"longitude":75.7873,"month":9,"timezone_as_float":5.5,"year":2026,"moon_option":"purnimanta"}'

One row per calendar day for a whole Gregorian month — the grid a panchang wall calendar prints. Each day carries sunrise, sunset, moonrise and moonset, the weekday in Sanskrit, the lunar month under both reckonings, the Vikram and Shaka years with their sixty-year cycle names, and the tithi, Moon sign and Moon nakshatra prevailing at that day's sunrise. Because a tithi or nakshatra usually changes partway through a day, each of those three carries an exit_time: the exact instant it gives way to the next, or null if it lasts past the following sunrise. That is what lets you render the familiar 'Vrishchika 01:08+' style labels. Pass year, month, latitude, longitude and UTC offset. moon_option chooses which reckoning the row's lunar_month field follows, 'purnimanta' (the default) or 'amanta'; both amanta_month and purnimanta_month are returned on every row regardless, so you can switch presentation without a second call. The response is {year, month, days} with one entry per day of that month.

Request fields

Field	Type	Required	Notes
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.
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.
month	integer	required	Month of birth as a number, 1-12. January is 1. min 1 · max 12
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.
year	integer	required	Year of birth as a number, e.g. 1990. Four digits. min 1800 · max 2400
moon_option	string	optional	`purnimantaamanta`

Full reference for this endpoint