Hindu calendar: vrats (Ekadashi with parana, Pradosh, Sankashti, Purnima, Amavasya, Masik Shivaratri)
Changed onEvery vrat of the year for the place. Ekadashi: the Smarta day (Ekadashi at sunrise; two sunrises: the first, unless Dashami touches it at arunodaya; Dwadashi with no sunrise: the day before) and the Vaishnava day where it differs (Dashami-viddha at arunodaya refused, Gauna day, Vanjuli mahadwadashi), each with its parana window outside Hari Vasara and within Dwadashi. Pradosh (Trayodashi at pradosha, named by weekday), Sankashti Chaturthi (Krishna Chaturthi at moonrise, with the moonrise), Masik Shivaratri (Krishna Chaturdashi at nishita), Purnima vrat and bath day, Darsha Amavasya and the Amavasya bath day. types narrows the list. Every New Delhi 2025 and 2026 date matches drikpanchang; parana windows within a minute.
Request
- Base URLhttps://api.astroway.info/v1
- AuthAPI key in header X-Api-Key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.
Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.
Headers
Unique per logical operation, kept across retries. For 24 hours from the first request, a repeat with the same key, method, path, body and query string returns the stored response with Idempotent-Replayed: true and costs 0 credits. The same key with a different body or query string is a 409 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running is a 409 IDEMPOTENCY_IN_PROGRESS. Only 2xx responses are kept. See /idempotency/.
Request body
Response
Successful calculation
Example response
{
"ok": true
}Changes
- info
endpoint added
- info