---
title: "Calculate planetary strength suite"
method: POST
path: "/v1/astro/strength"
tags: ["Advanced"]
---

# Calculate planetary strength suite

`POST /v1/astro/strength`

## Request

- Base URL: `https://api.asterwise.com`
- URL: `https://api.asterwise.com/v1/astro/strength`
- Auth: HTTP bearer

Builds a composite strength report including shadbala, divisional charts, ashtakavarga, and karakas from birth input. Returns a unified strength payload for all supported modules.

## Request body

- StrengthRequest
  - `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`

Composite strength report across astrology modules

- ApiResponseStrengthResponse
  - `success` boolean: True if the request succeeded
  - `message` string: Human-readable status message
  - `data` StrengthResponse, required: Strength report root. Includes ``shadbala``, ``bhavbala`` (keys ``"1"``…``"12"`` with ``bhavadhipati_bala``, ``bhava_dig_bala``, ``bhava_drik_bala``, ``total``), ``vimshopaka_bala`` (per-planet sixteen-varga score and threshold), ``divisional_charts``, ``ashtakavarga``, ``karakas``, ``birth_time_provided``, and optional ``graha_yuddha``. Shadbala follows B.V. Raman's worked example and Jagannatha Hora: the Sun's and the Moon's ``cheshta_bala`` is 0, because BPHS's Cheshta Bala for them (the Sun's Ayana, the Moon's Paksha) is counted in Kala Bala, where the Sun's ``ayana`` and the Moon's ``paksha`` are doubled (0–120). ``ayana`` uses the kranti (declination) of the planet's ecliptic longitude, true obliquity of date, latitude ignored, so it stays within 0–60 (0–120 for the doubled Sun). ``paksha`` takes each planet's nature in the chart (BPHS Ch.3, as in Jagannatha Hora): the Moon is benefic in Shukla paksha and malefic in Krishna paksha (so a waning Moon is strongest near Amavasya), Mercury follows his companions, Jupiter and Venus are benefic, the rest malefic. Vimshopaka ``threshold`` bands (BPHS Ch.45): ``extremely_auspicious`` (15 or more), ``good`` (10 or more), ``moderate`` (5 or more) and ``zero_capacity`` (below 5). Under BPHS scoring every varga earns at least a quarter of its weight (great enemy's sign), so the score is never below 5.0 and ``zero_capacity`` does not occur; it is kept in the set of values for compatibility.

## 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)