Skip to main content
POST/v1/astro/ashtakavarga

Ashtakavarga

Computes the Ashtakavarga system for a given birth chart. What is Ashtakavarga? Ashtakavarga is a Vedic system that assigns benefic points (bindus) to each house based on the positions of the 7 classical planets and the Lagna (ascendant). It is used to assess the relative strength of each house and to time events through transit analysis — a planet transiting a house with more bindus produces better results. What this endpoint returns: - bhinna — Bhinna Ashtakavarga (BAV): the raw contribution table for each planet and the Lagna. Each entry maps Sanskrit sign name (Mesha…Meena) to bindus in that sign. - bhinna_after_trikona — BAV after Trikona Shodana (triangular reduction). Points in trinal houses are equalised. Per-planet objects keyed by sign name. - bhinna_after_ekadhipatya — BAV after both Trikona and Ekadhipatya Shodana (lordship reduction). The most refined per-planet table, keyed by sign name. - sarva — Sarva Ashtakavarga (SAV): the raw sum across all 7 planets. Object keyed by sign name; 28+ bindus in a sign is considered strong. - sarva_reduced — SAV computed from the fully reduced planet tables. More accurate for transit timing. Keyed by sign name. - after_trikona / after_ekadhipatya — SAV-level reductions for backward compatibility, keyed by sign name. How to use bindus for transit timing: When a planet transits a house in its own Bhinna chart, the number of bindus in that house indicates how favourable the transit will be. 8 bindus is maximum, 0 is minimum. In the SAV, 30+ bindus in a house indicates strong positive results during transits through that house. Ayanamsa: All positions are sidereal. Default is Lahiri. Returns Bhinna Ashtakavarga (BAV) and Sarva Ashtakavarga (SAV) scores for all planets and houses.

Request parameters​

locationoptional
string | null
City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required.
nameoptional
string
Person name associated with the birth record
daterequired
string
Birth date in YYYY-MM-DD format
timeoptional
string | null
Birth time in HH:MM 24-hour format. If omitted, sunrise chart is used as fallback.
latitudeoptional
number | null
Latitude. Required if location not provided.
longitudeoptional
number | null
Longitude. Required if location not provided.
timezoneoptional
string | null
IANA timezone. Required if location not provided.
ayanamsaoptional
string
Sidereal ayanamsa mode used in calculations

Response fields​

success
boolean
True if the request succeeded
message
string
Human-readable status message
data
object
data.bhinna
object
Bhinna Ashtakavarga (BAV) for each planet plus Lagna. Keys: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Lagna. Each value maps Sanskrit sign name (Mesha…Meena) to bindu count for that sign.
data.bhinna_after_trikona
object
BAV after Trikona Shodana (triangular reduction). Keys: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn. Each value maps Sanskrit sign name to bindu count.
data.bhinna_after_ekadhipatya
object
BAV after both Trikona and Ekadhipatya Shodana (lordship reduction). Keys: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn. Each value maps Sanskrit sign name to bindu count. This is the most refined per-planet Ashtakavarga.
data.sarva
object
Sarva Ashtakavarga (SAV) — the raw sum of all 7 planet BAVs across 12 signs. Keys: Mesha through Meena.
data.sarva_reduced
object
Reduced SAV — sum of the 7 fully reduced planet BAVs (after both Trikona and Ekadhipatya Shodana). Keys: Mesha through Meena. More accurate than sarva for predictive work.
data.after_trikona
object
SAV after Trikona Shodana applied directly to the raw SAV. Keys: Mesha through Meena.
data.after_ekadhipatya
object
SAV after both Trikona and Ekadhipatya Shodana applied directly to the raw SAV. Keys: Mesha through Meena.
data.birth_time_provided
boolean
Whether a precise birth time was provided. False when birth time was not supplied or treated as unknown — calculations using this field will have lagna-dependent accuracy limits.

Errors​

Missing or invalid API key.
Upstream ephemeris service error.
API key tier does not include this endpoint.
Unexpected server error.
Too many requests in a short window.
Request body exceeds the size limit.
Referenced resource was not found.
Request body failed schema validation.