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

Sign transitions

Request bodyJSON

Paste an API key above to send.

Code snippet

curl -X POST https://yogataraapi.prahlad.app/api/astro/sign_transitions/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year":2026,"timezone_as_float":5.5}'

Every moment a planet crosses from one sidereal sign into the next, for a whole year — the event Indian astrology calls gochar, or sankranti in the Sun's case. The Sun's twelve crossings mark the solar months, Jupiter's and Saturn's are what long-range predictions hang on, and the Moon's come round every two and a half days. Send `year` and `timezone_as_float`. The response is `data.planets`, an object keyed by planet name, each holding a list of `{from_sign, to_sign, datetime}` in date order. Twelve bodies are covered: sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, truenode and meannode. Note that the lunar nodes appear under those two names rather than as rahu and ketu. Timestamps are UTC, and the crossing instant is the same everywhere on Earth — the offset you send decides which local calendar year the scan covers, so that a crossing late on 31 December UTC is correctly returned in the following year for an Indian viewer. Convert to local time for display. Crossings are located by walking day by day and then narrowing within the day, giving times good to a small fraction of a degree. The Moon alone contributes over 150 entries a year, so expect a sizeable response. The same figures appear inside `/api/planetary_details/` alongside eight other calculations; this endpoint returns only the transitions.

Request fields

Field	Type	Required	Notes
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.

Field

Type

Required

Notes

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.

Full reference for this endpoint