Hindu calendar: ICS feed of festivals and vrats
Changed onThe festivals and vrats of a year for a place as an iCalendar file (text/calendar, RFC 5545): one all-day event per observance, the rule, tithi window, parana and source in the description, a stable UID per festival, date and place. Query: year, latitude, longitude, timezone (IANA or auto), include (festivals, vrats or single vrat types, comma separated; default festivals,vrats), tradition. The key travels in X-Api-Key, so fetch it from your server and serve the file to calendar apps; it is priced as one festivals call.
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
Gregorian year; events are those dated in it.
Latitude in decimal degrees, north positive.
Longitude in decimal degrees, east positive.
IANA zone name, or auto to look it up from the coordinates. Followed day by day, summer time included.
Comma list: festivals, vrats, or single vrat types (ekadashi, pradosh, sankashti, purnima, amavasya, masik-shivaratri).
Whose reckoning decides the day where traditions differ (Rama Navami, Janmashtami).
Ayanamsa id; 1 is Lahiri.
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.
Response
iCalendar (RFC 5545): one all-day VEVENT per festival and vrat, the rule, tithi window, parana and source in DESCRIPTION.
Changes
- info
endpoint added
- info