--- title: "Ashtakavarga" method: POST path: "/v1/astro/ashtakavarga" tags: ["Advanced"] --- # Ashtakavarga `POST /v1/astro/ashtakavarga` ## Request - Base URL: `https://api.asterwise.com` - URL: `https://api.asterwise.com/v1/astro/ashtakavarga` - Auth: HTTP bearer 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, BPHS Ch.70; a sign counts as occupied only when one of the seven grahas is in it). 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** — legacy: the reductions applied to the summed SAV, kept for backward compatibility. Not classical values (Shodhana is applied per planet); prefer **sarva_reduced**. **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 body - AshtakavargaRequest - `location` string, nullable: City name to resolve to lat/lon/tz automatically. Example: 'Mumbai' or 'New Delhi, India'. If provided, latitude, longitude and timezone are not required. - `name` string: Person name associated with the birth record - `date` string, required: Birth date in YYYY-MM-DD format - `time` string, nullable: Birth time in HH:MM 24-hour format. If omitted, sunrise chart is used as fallback. - `latitude` number, nullable: Latitude. Required if location not provided. - `longitude` number, nullable: Longitude. Required if location not provided. - `timezone` string, nullable: IANA timezone. Required if location not provided (unless utc_offset is given). For dates before the zone adopted a standard time, the birthplace's local mean time (longitude / 15 hours) is used. - `utc_offset` string, nullable: Optional explicit UTC offset of the birth time, as ±HH:MM or ±HH:MM:SS (e.g. '+04:51:31' for Bombay mean time). Overrides the offset `timezone` would give. Use it when the birth record states the offset, or for historical local times the IANA database cannot represent. - `ayanamsa` 'lahiri' | 'raman' | 'kp' | 'tropical': Sidereal ayanamsa mode used in calculations ## Response `200` Successful Response - ApiResponseAshtakavargaResponse - `success` boolean: True if the request succeeded - `message` string: Human-readable status message - `data` AshtakavargaResponse, required - `bhinna` object, required: 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. - `bhinna_after_trikona` object, required: BAV after Trikona Shodana (triangular reduction). Keys: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn. Each value maps Sanskrit sign name to bindu count. - `bhinna_after_ekadhipatya` object, required: BAV after both Trikona and Ekadhipatya Shodana (lordship reduction, BPHS Ch.70: occupancy by the seven grahas only — not the Lagna or the nodes; beside an occupied sign, an empty sign with fewer bindus is cleared and one with more is cut to the occupied sign's number). 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. - `sarva` object, required: Sarva Ashtakavarga (SAV) — the raw sum of all 7 planet BAVs across 12 signs. Keys: Mesha through Meena. - `sarva_reduced` object, required: Reduced SAV — sum of the 7 fully reduced planet BAVs (after both Trikona and Ekadhipatya Shodana), the input to Shodhya Pinda. Keys: Mesha through Meena. Transit grading uses the raw tables, not these. - `after_trikona` object, required: Legacy (kept for v1 compatibility): Trikona Shodana applied to the summed SAV. Classical Shodhana is applied to each planet's BAV (see bhinna_after_trikona); this is not a classical value. Keys: Mesha through Meena. - `after_ekadhipatya` object, required: Legacy (kept for v1 compatibility): Trikona and Ekadhipatya Shodana applied to the summed SAV. Not a classical value; use sarva_reduced. Keys: Mesha through Meena. - `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. ## Other responses - `401`: Authentication failed - `403`: Authorization failed - `404`: Resource not found - `413`: Payload too large - `422`: Validation error - `429`: Rate limit exceeded - `500`: Internal error - `502`: Upstream provider error - `503`: Service unavailable --- [API](https://skmtc.dev/asterwise/apis/asterwise-api.md) · [All operations](https://skmtc.dev/asterwise/apis/asterwise-api/llms.txt) · [OpenAPI document](https://skmtc.dev/asterwise/apis/asterwise-api/revisions/3c4bbb1194e2?raw)