Dashas: Kalachakra Pratyantardasha
curl -X POST https://api.astroway.info/v1/vedic/dashas/kalachakra/pratyantar \ -H "X-Api-Key: aw_live_..." \ -H "Content-Type: application/json" \ -d '{ "date": "1947-08-15", "time": "02:00:00", "timezoneOffset": 5.5, "latitude": 27.49, "longitude": 77.67, "targetDate": "2026-05-06" }'const res = await fetch('https://api.astroway.info/v1/vedic/dashas/kalachakra/pratyantar', { method: 'POST', headers: { 'X-Api-Key': process.env.ASTROWAY_API_KEY, 'Content-Type': 'application/json', }, body: JSON.stringify({ "date": "1947-08-15", "time": "02:00:00", "timezoneOffset": 5.5, "latitude": 27.49, "longitude": 77.67, "targetDate": "2026-05-06" }),});const { ok, data, error } = await res.json();if (!ok) throw new Error(error.message);console.log(data);import os, requests
r = requests.post( 'https://api.astroway.info/v1/vedic/dashas/kalachakra/pratyantar', headers={'X-Api-Key': os.environ['ASTROWAY_API_KEY'], 'Content-Type': 'application/json'}, json={ 'date': "1947-08-15", 'time': "02:00:00", 'timezoneOffset': 5.5, 'latitude': 27.49, 'longitude': 77.67, 'targetDate': "2026-05-06" },)result = r.json()if not result['ok']: raise RuntimeError(result['error']['message'])print(result['data'])<?phpuse GuzzleHttp\Client;
$client = new Client(['base_uri' => 'https://api.astroway.info/v1/']);$r = $client->post('vedic/dashas/kalachakra/pratyantar', [ 'headers' => ['X-Api-Key' => getenv('ASTROWAY_API_KEY')], 'json' => [ 'date' => '1947-08-15', 'time' => '02:00:00', 'timezoneOffset' => 5.5, 'latitude' => 27.49, 'longitude' => 77.67, 'targetDate' => '2026-05-06', ],]);$result = json_decode($r->getBody(), true);if (!$result['ok']) throw new \RuntimeException($result['error']['message']);print_r($result['data']);Kalachakra Pratyantardasha: 3-level cascade (MD → AD → 9 PDs). Recursion preserves the natal chakra-row and paramayu.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.
Example
planets.name,planets.longitudeRound every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.
Example
4Request Body required
Section titled “Request Body required ”Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as “Placidus” is refused, and the case matters because I and i are two different Sunshine systems.
object
Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.
IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
Example
{ "date": "1947-08-15", "time": "02:00:00", "timezoneOffset": 5.5, "latitude": 27.49, "longitude": 77.67, "targetDate": "2026-05-06"}Responses
Section titled “ Responses ”Successful calculation
object
object
object
object
object
object
object
object
Example
{ "ok": true, "data": { "system": "Kalachakra", "level": "pratyantar", "ayanamsa": 23.125454161038185, "moonSiderealLongitude": 95.24121106113016, "nakshatra": { "number": 8, "name": "Pushya", "nameRu": "Пушья", "nameUk": "Пушья", "ruler": "Saturn", "startDeg": 93.3333, "endDeg": 106.6667, "pada": 1 }, "initial": { "initialSign": 5, "initialSignName": "Virgo", "initialSignLord": 2, "initialSignLordName": "Mercury", "nakshatra": 8, "nakshatraName": "Pushya", "pada": 1, "direction": "savya", "chakraGroup": "Bharani-group", "effectivePada": 2, "paramayu": 85, "chakraSequence": [ { "sign": 9, "signName": "Capricorn", "years": 4 } ], "balanceYears": 1, "balanceMonths": 4, "balanceDays": 6, "elapsedYears": 48.650882058819164 }, "currentMaha": { "sign": 1, "signName": "Taurus", "signLord": 3, "signLordName": "Venus", "startJd": 2460664.1194946826, "endJd": 2466508.1194946826, "startDate": "2024-12-19 20:22", "endDate": "2040-12-19 20:22", "durationYears": 16 }, "currentAntar": { "sign": 1, "signName": "Taurus", "signLord": 3, "signLordName": "Venus", "startJd": 2460664.1194946826, "endJd": 2461790.67371155, "startDate": "2024-12-19 20:22", "endDate": "2028-01-20 09:40", "durationYears": 3.0843373493975905 }, "periods": [ { "signIndex": 1, "signName": "Taurus", "signLord": 3, "signLordName": "Venus", "rowIndex": 0, "startJd": 2460664.1194946826, "endJd": 2460881.286572633, "startDate": "2024-12-19 20:22", "endDate": "2025-07-25 00:22", "durationYears": 0.5945710553055596 } ] }}Validation error
Example
{ "ok": false, "error": { "code": "INVALID_INPUT", "message": "Validation failed: date: Date must be YYYY-MM-DD", "details": [ { "path": "date", "message": "Date must be YYYY-MM-DD" } ] }}Missing or invalid API key
Example
{ "ok": false, "error": { "code": "INVALID_API_KEY", "message": "Invalid API key" }}