curl -X POST https://yogataraapi.prahlad.app/api/astro/vasa-segments/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"2026-09-09T06:00:00+05:30","latitude":26.9124,"longitude":75.7873,"timezone_as_float":5.5}'Where fire and Shiva are held to reside through the day, as timed segments. Two muhurta considerations consulted for the same kinds of decision — homa and other fire rituals for agni vasa, anything Shiva-facing for shiva vasa. Both come back as lists of segments rather than a single state for the day, because either can change part-way through it. Each segment carries its own start and end, so you can say "Prithvi until 07:01, then Akasha" instead of picking one label for the whole day and being wrong for half of it. The agni segments flag `is_patala`, which is the state those rituals are specifically avoided in. Hindi labels come through as `state_hi`.
| 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 |
| dhuma_vyatipata_relation | string | optional | 360_minus_dhumadhuma_plus_53_20 |
| eccentric_anomaly | number (double) | optional | |
| eccentricity | number (double) | optional | |
| gulika_portion | string | optional | saturneighth |
| gulika_rises_at | string | optional | beginningmiddleend |
| kala_mrityu_rise_at | string | optional | beginningmiddleend |
| 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. |
| mandi_portion | string | optional | saturneighth |
| mandi_rises_at | string | optional | beginningmiddleend |
| mean_anomaly | number (double) | optional | |
| mode | string | optional | |
| nakshatras | string | optional | |
| samvata_type | string | optional | |
| tolerance | number (double) | optional |