curl -X POST https://yogataraapi.prahlad.app/api/astro/tajika/aspects/ \
-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,"raasi":0,"planet":"Moon","planet1":"Mercury","planet2":"Saturn"}'Every Tajika aspect to one sign and one planet, in a single call. Tajika — the Persian-derived branch used for varshaphala, the annual chart — reads aspects by ANGLE the way Western astrology does, rather than by the whole-sign drishti of parashari astrology. Conjunction, semi-sextile, sextile, square, trine and opposition are each returned as the signs that make them, spelled out by name, alongside the tradition's own benefic / malefic / neutral grouping of the same set. Also returned: whether your chosen pair of planets is inside its deeptamsa — the orb within which a Tajika aspect is held to actually operate — and whether the two are applying or separating. That last distinction is what separates an ithasala from an eesarpha, and so is the question most Tajika readings turn on. Twenty-seven engine keys for one credit. Reaching the same answers through /api/astro/tajaka/ costs a credit per call, requires you to supply a raasi, a planet, two more planets, a node and a house on every request whichever key you wanted, and returns unlabelled positional arrays whose sign indices are zero-based — so reading index 4 as Taurus rather than Leo gives a confident wrong answer. Here every field defaults and every index is named.
| 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 |
| house | integer | optional | House to test for benefic/malefic aspect, zero-based. min 0 · max 11 |
| 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 | The planet whose aspects are read. |
| planet1 | string | optional | |
| planet2 | string | optional | planet1 and planet2 are the PAIR tested for deeptamsa and approach; they do not affect the aspect lists. |
| raasi | integer | optional | Sign to read aspects to, ZERO-BASED: 0 is Aries, 11 Pisces. min 0 · max 11 |
| 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 |