/api/astro/pancha-vargeeya-bala/1 creditPancha vargeeya bala
Pancha vargeeya bala: the five-fold strength, with the components that run. The total is returned with exaltation, navamsa and drekkana strength. Kshetra bala and hadda bala are deliberately NOT included: both raise a TypeError in the engine because the configuration does not pass the argument they require, and one failing key fails the whole request — so asking for them would take the working components down too. The response names what it omitted and why.
https://yogataraapi.prahlad.app/api/astro/pancha-vargeeya-bala/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 |
| asc_house | integer | optional | Ascendant house number. Defaults to 1. min 1 · max 12 |
| 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. |
| timezone | number (double) | optional | 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. min -12 · max 14 |
| 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/pancha-vargeeya-bala/ \
-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":5.5,"asc_house":1}'Response
{
"data": {
"scale": "0-10",
"total": {
"Sun": 6.42,
"Moon": 2.26,
"Mars": 9.29,
"Mercury": 5.3,
"Jupiter": 4,
"Venus": 4.04,
"Saturn": 9.93
},
"components": [
{
"bala": "uchcha_bala",
"measures": "Exaltation strength",
"by_planet": {
"Sun": 18.33,
"Moon": 0.07,
"Mars": 11.46,
"Mercury": 0.26,
"Jupiter": 5.01,
"Venus": 11.44,
"Saturn": 12.14
}
},
{
"bala": "navamsa_bala_simple",
"measures": "Navamsa strength",
"by_planet": {
"Sun": 1.25,
"Moon": 2.5,
"Mars": 2.5,
"Mercury": 1.25,
"Jupiter": 1.25,
"Venus": 2.5,
"Saturn": 5
}
},
{
"bala": "drekkana_bala_simple",
"measures": "Drekkana strength",
"by_planet": {
"Sun": 5,
"Moon": 5,
"Mars": 2.5,
"Mercury": 2.5,
"Jupiter": 10,
"Venus": 2.5,
"Saturn": 2.5
}
}
],
"components_omitted": [
"kshetra_bala",
"hadda_bala"
],
"omission_reason": "Both raise TypeError in the engine: the configuration does not pass the argument they require."
},
"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.