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

Compatibility: Dashakoota (10-fold 39-point)

POST
/vedic/compatibility/dashakoota
request.sh
curl -X POST https://api.astroway.info/v1/vedic/compatibility/dashakoota \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "chart1": { "date": "1990-05-15", "time": "15:30:00", "timezone": "Europe/Kyiv", "latitude": 50.45, "longitude": 30.52 }, "chart2": { "date": "1985-11-03", "time": "09:15:00", "timezone": "Europe/Kyiv", "latitude": 48.46, "longitude": 35.04 } }'

Extended matchmaking adding Mahendra(2) + Vedha(1) on top of Ashtakoot 36 = 39 max. Mahendra: birth-star count 4/7/10/13/16/19/22/25 → 2pt; else 0. Vedha: 13 canonical mutually-obstructing nakshatra pairs → 0pt blocked, 1pt clear.

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

Pair of natal charts for relationship calculations: synastry, composite, davison.

object
chart1 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
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
key additional
nullable
chart2 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
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
key additional
nullable
Example
{
"chart1": {
"date": "1990-05-15",
"time": "15:30:00",
"timezone": "Europe/Kyiv",
"latitude": 50.45,
"longitude": 30.52
},
"chart2": {
"date": "1985-11-03",
"time": "09:15:00",
"timezone": "Europe/Kyiv",
"latitude": 48.46,
"longitude": 35.04
}
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
method
string
nullable
school
string
nullable
boy
object
moonLongitude
number
nullable
nakshatra
number
nullable
girl
object
moonLongitude
number
nullable
nakshatra
number
nullable
total
number
nullable
max
number
nullable
threshold
string
nullable
points
object
varna
object
score
number
nullable
max
number
nullable
boy
string
nullable
girl
string
nullable
rule
string
nullable
vashya
object
score
number
nullable
max
number
nullable
boyGroup
string
nullable
girlGroup
string
nullable
tara
object
score
number
nullable
max
number
nullable
fromBoyToGirl
number
nullable
fromGirlToBoy
number
nullable
yoni
object
score
number
nullable
max
number
nullable
boyYoni
string
nullable
girlYoni
string
nullable
relationship
string
nullable
grahaMaitri
object
score
number
nullable
max
number
nullable
boyRuler
string
nullable
girlRuler
string
nullable
relationship
string
nullable
gana
object
score
number
nullable
max
number
nullable
boyGana
string
nullable
girlGana
string
nullable
bhakoot
object
score
number
nullable
max
number
nullable
fromBoyToGirl
number
nullable
fromGirlToBoy
number
nullable
dosha
string
nullable
nadi
object
score
number
nullable
max
number
nullable
boyNadi
string
nullable
girlNadi
string
nullable
dosha
nullable
cancelled
nullable
doshas
Array<string>
nullable
recommendation
string
nullable
mahendra
object
score
number
nullable
max
number
nullable
distance
number
nullable
vedha
object
score
number
nullable
max
number
nullable
blocked
boolean
nullable
dashakootaTotal
number
nullable
dashakootaMax
number
nullable
Example
{
"ok": true,
"data": {
"method": "dashakoota",
"school": "parashara",
"boy": {
"moonLongitude": 273.178879897163,
"nakshatra": 21
},
"girl": {
"moonLongitude": 77.32226130757923,
"nakshatra": 6
},
"total": 24,
"max": 36,
"threshold": "good",
"points": {
"varna": {
"score": 1,
"max": 1,
"boy": "vaishya",
"girl": "shudra",
"rule": "boy varna >= girl varna → 1pt"
},
"vashya": {
"score": 1.5,
"max": 2,
"boyGroup": "jalachara",
"girlGroup": "manava"
},
"tara": {
"score": 1.5,
"max": 3,
"fromBoyToGirl": 3,
"fromGirlToBoy": 6
},
"yoni": {
"score": 2,
"max": 4,
"boyYoni": "mongoose",
"girlYoni": "dog",
"relationship": "neutral"
},
"grahaMaitri": {
"score": 4,
"max": 5,
"boyRuler": "Saturn",
"girlRuler": "Mercury",
"relationship": "F-N"
},
"gana": {
"score": 6,
"max": 6,
"boyGana": "manushya",
"girlGana": "manushya"
},
"bhakoot": {
"score": 0,
"max": 7,
"fromBoyToGirl": 6,
"fromGirlToBoy": 8,
"dosha": "6-8"
},
"nadi": {
"score": 8,
"max": 8,
"boyNadi": "antya",
"girlNadi": "adi",
"dosha": null,
"cancelled": null
}
},
"doshas": [
"Bhakoot Dosha: 6-8"
],
"recommendation": "good (24/36), note: Bhakoot Dosha: 6-8; cancellation rules may apply (same-Moon-sign or same-nakshatra exempts Nadi).",
"mahendra": {
"score": 2,
"max": 2,
"distance": 13
},
"vedha": {
"score": 1,
"max": 1,
"blocked": false
},
"dashakootaTotal": 27,
"dashakootaMax": 39
}
}

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"
}
}
Корисно?