/api/astro/tajika/yogas/1 creditTajika yogas
The thirteen Tajika yogas, as named results rather than thirteen keys. These are the combinations varshaphala is actually judged by. Ithasala — an applying aspect between the relevant lords, the promise of a thing coming about — and eesarpha — a separating one, the promise lapsing — are the two a reading usually turns on; the rest qualify them. Each yoga reports whether it is present, keeping whatever detail the engine attaches to it, and the pair- and triple-finding results are grouped separately because those answer which planets rather than whether. As with /api/astro/tajika/aspects/, the parent requires a planet and two more planets and a node on every call regardless of which yoga you asked for. Here they default.
https://yogataraapi.prahlad.app/api/astro/tajika/yogas/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 |
| 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 | truemean |
| planet | string | optional | |
| planet1 | string | optional | |
| planet2 | string | optional | |
| 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 |
Example request
curl -X POST https://yogataraapi.prahlad.app/api/astro/tajika/yogas/ \
-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,"planet":"Moon","planet1":"Mars","planet2":"Saturn"}'Response
{
"data": {
"planets": {
"planet": "Moon",
"pair": [
"Mars",
"Saturn"
]
},
"yogas": {
"ishkavala": {
"present": true
},
"induvara": {
"present": false
},
"ithasala": {
"present": false,
"detail": [
1
]
},
"eesarpha": {
"present": false
},
"yamaya": {
"present": false
}
},
"combinations": {
"nakta_triples": [],
"yamaya_triples": [],
"ithasala_pairs": [],
"eesarpha_pairs": [],
"manahoo_pairs": [],
"kamboola_pairs": [
false,
[],
[]
],
"gairi_kamboola_pairs": null,
"khallasara_pairs": null
}
},
"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.