curl -X POST https://yogataraapi.prahlad.app/api/astro/raja_yoga/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keys":["get_raja_yoga_details_for_all_charts"],"date_time":"2025-07-14T11:00:37.673Z","latitude":13,"longitude":77.5946,"timezone":5.5}'A raja yoga is a combination in a birth chart said to confer status and success. The core case is an association between the lord of an angular house (1, 4, 7, 10) and the lord of a trine (1, 5, 9) — the two conjoined, aspecting each other, or exchanging signs. This endpoint checks the three named variants the engine implements: Vipareeta raja yoga (the lords of the difficult sixth, eighth and twelfth houses falling among themselves), Neecha Bhanga raja yoga (a debilitated planet whose debilitation is cancelled) and Dharma-Karmadhipati raja yoga (the ninth and tenth lords in association). One key, `get_raja_yoga_details_for_all_charts`, which runs the checks across every divisional chart the engine knows rather than the birth chart alone. Its value is a three-element array: an object mapping each yoga found to its details, the number found, and the number of checks made — three yoga types across twenty-three divisional charts, so 69. Each detail entry is a list of strings: first a line naming the divisional chart and the planet pairs responsible, such as `"D1-Raja Yoga Pairs: [Viyaazhan-Sani]"`, then the yoga's name, its definition and its predicted effects. Two notes on reading the output. Planet names inside the pairs line are given in Tamil transliteration whatever else you send: Suriyan is the Sun, Chandran the Moon, Sevvay Mars, Budhan Mercury, Viyaazhan Jupiter, VeLLi Venus and Sani Saturn. And because the results from all divisional charts are merged into one object keyed by yoga name, each yoga appears once only, reported against the earliest divisional chart in which it was found — a `D4-` prefix means the birth chart itself did not have it. One caveat before you build on this: the underlying calculation currently substitutes a fixed date for the `date_time` you send, so the result responds to the location fields but not to the birth date. Check it against a chart you know before relying on it.
| 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. |
| keys | array | required | 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) | 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 -90 · max 90 |
| 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 | number (double) | required | UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30). Identical in meaning to timezone_as_float, which other endpoints call the same thing by a different name. |
Ask for exactly the calculations you want by listing them in keys. An unknown key rejects the whole request, and you are charged 1 credit however many you ask for — so batch them.
| Key | Extra fields needed | Description | |
|---|---|---|---|
| get_raja_yoga_details_for_all_charts | — | Scans every divisional chart for the three raja yoga variants the engine implements — Vipareeta, Neecha Bhanga and Dharma-Karmadhipati. Returns a three-element array: an object keyed by yoga name holding that yoga's details, the count found, and the number of checks made (69, being three yoga types across twenty-three charts). Each detail value is a list of strings — the divisional chart and responsible planet pairs, then the yoga's name, definition and effects — and because the charts' results are merged into one object, a yoga appears once only, against the earliest chart in which it was found. |