Every planet's movement from one nakshatra to the next across a calendar year, with each crossing resolved to about a second. This is the 'planet nakshatra gochar' table: when Saturn leaves Purva Bhadrapada, when Jupiter enters Pushya, when the Moon changes star — the events transit predictions are timed from.
granularity chooses the resolution. 'nakshatra' uses the 13°20' divisions and returns from and to as plain names; 'pada' uses the 3°20' quarters and returns from and to as {nakshatra, pada} objects instead. Set use_28_nakshatras to true to include Abhijit as a twenty-eighth division.
Pass year and timezone_as_float. The offset decides where the local year starts and ends, but the returned timestamps are UTC — convert them yourself for display. The response is {year, granularity, planets}, where planets is keyed by name (sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, rahu, ketu), each holding a chronological list of {from, to, datetime}. The Moon alone produces over three hundred nakshatra transitions in a year and around fourteen hundred pada transitions, so pada responses are large.
Request fields
Field
Type
Required
Notes
granularity
string
required
nakshatrapada
year
integer
required
Year of birth as a number, e.g. 1990. Four digits.
min 1800 · max 2400
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.