/api/astro/rashi-aspects/1 creditWhat a sign aspects
What one sign aspects, and which planets are its baadhaka. Rashi drishti — sign-to-sign aspect — is a Jaimini idea rather than a Parashari one: signs aspect signs regardless of what stands in them. The baadhaka, the obstructing lord, is returned alongside because it is read from the same sign. Signs are numbered 1 for Aries through 12 for Pisces. The engine underneath numbers them from zero, so this endpoint converts — verified against the baadhaka rule for all twelve signs (movable afflicted from the 11th, fixed from the 9th, dual from the 7th).
https://yogataraapi.prahlad.app/api/astro/rashi-aspects/Authentication
Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.
X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/jsonRequest 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. |
| 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_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. |
| node | string | optional | |
| planet | string | optional | |
| raasi | integer | optional | Sign number, 1 = Aries through 12 = Pisces. min 1 · max 12 |
Example request
curl -X POST https://yogataraapi.prahlad.app/api/astro/rashi-aspects/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"1990-05-10T19:55:00+05:30","latitude":26.9124,"longitude":75.7873,"timezone_as_float":5.5,"node":"true","raasi":5}'Response
{
"data": {
"raasi": 5,
"sign": "Leo",
"aspects_houses": [
6,
12,
3
],
"aspects_raasis": [
0,
6,
9
],
"baadhaka": {
"rasi_number": 0,
"sign": "Aries",
"planets": [
"Mars"
],
"raw": [
0,
[
2
]
]
}
},
"status": 200,
"is_error": false,
"message": "successful"
}Captured from a real call using the exact request above. Results sit under data.
Errors
Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.