Перейти до вмісту
AstroWay/api v2.254.12 · docs
усі системи в нормі

Kundli (one call)

POST
/vedic/kundli
request.sh
curl -X POST https://api.astroway.info/v1/vedic/kundli \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "date": "1990-05-15", "time": "15:30:00", "timezone": "Europe/Kyiv", "latitude": 50.45, "longitude": 30.52, "targetDate": "2026-10-06" }'

A kundli card in one call: D1 lagna and the nine grahas with sign names, the Moon nakshatra and pada, the running Vimshottari maha and antar at targetDate (default now), and the Parashari yogas and doshas with a present list of the ones found. Each part is the same answer as its own route (/vedic/varga/D1, /vedic/dashas/vimshottari/antar, /vedic/yogas/parashara/full, /vedic/doshas/parashara/full). latitude and longitude are required; time is HH:mm:ss or HH:mm. nakshatra.nameLocalized is the name in the requested language (Devanagari for hi, the Cyrillic forms for uk and ru, the international transliteration elsewhere). 50 credits.

fields
string

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.longitude
precision
integer
<= 15

Round 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
4
Media type application/json

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
date required
string
/^\d{4}-\d{2}-\d{2}$/
time required
string
/^\d{2}:\d{2}(:\d{2})?$/
timezoneOffset

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.

number
0 nullable >= -14 <= 14
timezone

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.

string
latitude required
number
>= -90 <= 90
longitude required
number
>= -180 <= 180
houseSystem
string
default: P
Allowed values: P K R C E W B M O A T V D F G H I i L N Q S U X Y
name
string
""
city
string
""
zodiacType
string
Allowed values: tropical sidereal
ayanamsaId
number
nullable
ayanamsa

Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.

string
Allowed values: fagan-bradley lahiri de-luce raman krishnamurti kp yukteshwar jn-bhasin true-citra djwhal-khul
cosmogram
boolean
targetDate
string
/^\d{4}-\d{2}-\d{2}$/
targetTime
string
/^\d{2}:\d{2}(:\d{2})?$/
targetTzOffset
number
nullable
Example
{
"date": "1990-05-15",
"time": "15:30:00",
"timezone": "Europe/Kyiv",
"latitude": 50.45,
"longitude": 30.52,
"targetDate": "2026-10-06"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
ayanamsa
number
nullable
lagna
object
longitude
number
nullable
sign
number
nullable
degreeInSign
number
nullable
signName
string
nullable
grahas
Array<object>
nullable
object
name
string
nullable
longitude
number
nullable
sign
number
nullable
degreeInSign
number
nullable
isRetrograde
boolean
nullable
signName
string
nullable
nakshatra
object
number
number
nullable
name
string
nullable
nameRu
string
nullable
nameUk
string
nullable
ruler
string
nullable
startDeg
number
nullable
endDeg
number
nullable
pada
number
nullable
dasha
object
system
string
nullable
maha
object
planet
number
nullable
planetName
string
nullable
startJd
number
nullable
endJd
number
nullable
startDate
string
nullable
endDate
string
nullable
durationYears
number
nullable
antar
object
planet
number
nullable
planetName
string
nullable
startJd
number
nullable
endJd
number
nullable
startDate
string
nullable
endDate
string
nullable
durationYears
number
nullable
yogas
object
present
Array
nullable
dhana
object
present
boolean
nullable
contributingPlanets
Array
nullable
doshas
object
present
Array<string>
nullable
mangal
object
present
boolean
nullable
severity
string
nullable
Example
{
"ok": true,
"data": {
"ayanamsa": 23.7225,
"lagna": {
"longitude": 146.2454,
"sign": 4,
"degreeInSign": 26.2454,
"signName": "Leo"
},
"grahas": [
{
"name": "Sun",
"longitude": 30.6502,
"sign": 1,
"degreeInSign": 0.6502,
"isRetrograde": false,
"signName": "Taurus"
},
{
"name": "Moon",
"longitude": 273.1789,
"sign": 9,
"degreeInSign": 3.1789,
"isRetrograde": false,
"signName": "Capricorn"
},
{
"name": "Ketu",
"longitude": 106.5326,
"sign": 3,
"degreeInSign": 16.5326,
"isRetrograde": true,
"signName": "Cancer"
}
],
"nakshatra": {
"number": 21,
"name": "Uttara Ashadha",
"nameRu": "Уттара Ашадха",
"nameUk": "Уттара Ашадха",
"ruler": "Sun",
"startDeg": 266.6667,
"endDeg": 280,
"pada": 2
},
"dasha": {
"system": "Vimshottari",
"maha": {
"planet": 11,
"planetName": "Rahu",
"startJd": 2455357.3655195693,
"endJd": 2461931.8655195693,
"startDate": "2010-06-10 00:46",
"endDate": "2028-06-09 12:46",
"durationYears": 18
},
"antar": {
"planet": 1,
"planetName": "Moon",
"startJd": 2461000.4780195695,
"endJd": 2461548.3530195695,
"startDate": "2025-11-21 03:28",
"endDate": "2027-05-23 00:28",
"durationYears": 1.5
}
},
"yogas": {
"present": [],
"dhana": {
"present": false,
"contributingPlanets": []
}
},
"doshas": {
"present": [
"mangal",
"shrapit",
"grahan"
],
"mangal": {
"present": true,
"severity": "strong"
}
}
}
}

Validation error

Media type application/json
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

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_API_KEY",
"message": "Invalid API key"
}
}
Корисно?