curl -X POST https://yogataraapi.prahlad.app/api/astro/traditional/almuten/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"1990-08-15T10:30:00+05:30","latitude":26.9124,"longitude":75.7873,"timezone_as_float":5.5}'Which planet has most dignity over the chart, and over each of its key points. Traditional astrology asks not only where the planets are but which of them is strongest over a given degree. The almuten is the answer: the planet holding the most weighted dignity there. Returned three ways. `by_point` gives the almuten of the Sun, Moon, ascendant, midheaven and part of fortune, with every candidate's score so you can see the margin. `by_planet` totals each planet across all of them. `almuten_figuris` is the overall winner — the chart's ruler in the medieval scheme. Only dignities count, not debilities: an almuten asks who rules a degree, not who is weak in it, so no score is ever negative. The part of fortune reverses by sect — ascendant + Moon − Sun by day, the reverse by night — which is the step most implementations skip. Ties are reported as ties. Where two planets score equally, `tied` lists them and the almuten is null, because breaking a tie silently would be an opinion presented as a calculation.
| 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. |
| latitude | number (double) | required | 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. min -89.9 · max 89.9 |
| longitude | number (double) | required | 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. min -180 · max 180 |
| timezone_as_float | number (double) | required | 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 |
| 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. |