POSThttps://yogataraapi.prahlad.app/api/astro/western/progressions/

Secondary progressions

Request bodyJSON

Paste an API key above to send.

Code snippet

curl -X POST https://yogataraapi.prahlad.app/api/astro/western/progressions/ \
  -H "X-API-Key: $OCCULT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date_time":"1990-05-10T19:55:00+05:30","timezone_as_float":5.5,"latitude":26.9124,"longitude":75.7873,"progressed_to":"2026-05-10T00:00:00+00:00","orb_factor":1}'

Secondary progressions: a day of ephemeris for a year of life. The chart is advanced by reading the sky one DAY after birth for each YEAR lived, so a fortieth birthday is read from the fortieth day of life. It is the oldest predictive technique in Western astrology, and the reason a progressed Moon moves about a degree a month while progressed Pluto barely moves at all across a whole lifetime. Give the date you want the chart for in `progressed_to`; the endpoint works out the elapsed years and the ephemeris date itself and reports both, so the conversion is visible rather than implied. Returns the progressed positions, the natal ones beside them, and every aspect from the progressed chart to the natal — which is how progressions are actually read.

Request fields

Field	Type	Required	Notes
date_time	string (date-time)	required	The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers.
progressed_to	string (date-time)	required	The date to progress the chart to. One day of ephemeris time is read for each year between birth and this date.
keys	array	optional	Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls.
latitude	number (double)	optional	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)	optional	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.
orb_factor	number (double)	optional	Scale every aspect orb. 0.5 halves them, 2 doubles them. min 0.1 · max 2
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. min -12 · max 14

Full reference for this endpoint