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

Porutham: Vedhai

POST
/vedic/compatibility/porutham/vedha
request.sh
curl -X POST https://api.astroway.info/v1/vedic/compatibility/porutham/vedha \
-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 } }'

Vedha porutham alone: 12 mutually piercing star pairs plus the Mrigashira-Chitra-Dhanishta triad. Same function as the factor inside /porutham.

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
Idempotency-Key
string
>= 1 characters <= 255 characters /^[\x21-\x7E]+$/

Unique per logical operation, kept across retries. For 24 hours from the first request, a repeat with the same key, method, path, body and query string returns the stored response with Idempotent-Replayed: true and costs 0 credits. The same key with a different body or query string is a 409 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running is a 409 IDEMPOTENCY_IN_PROGRESS. Only 2xx responses are kept. See /idempotency/.

Example
01HXY2A7ZM0ABCDEF
Media type application/json

Two charts for South Indian Porutham. chart1 is the groom, chart2 the bride.

object
chart1 required
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
chart2 required
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
school

Porutham school. tamil (default) or kerala; they differ on Dinam, Stree Deergham, Rasi and on which factors are essential.

string
Allowed values: tamil kerala
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
groom
object
star
number
nullable
starName
string
nullable
bride
object
star
number
nullable
starName
string
nullable
factor
string
nullable
verdict
string
nullable
pass
boolean
nullable
score
number
nullable
rule
string
nullable
source
string
nullable
basis
string
nullable
detail
object
vedha
boolean
nullable
Example
{
"ok": true,
"data": {
"method": "porutham-vedha",
"school": "tamil",
"groom": {
"star": 21,
"starName": "Uttara Ashadha"
},
"bride": {
"star": 6,
"starName": "Ardra"
},
"factor": "vedhai",
"verdict": "uttamam",
"pass": true,
"score": 1,
"rule": "The two stars are not a vedha pair.",
"source": "findyourfate.com, 10 Porutham (Tamil manual tables); hindutone.com, The 10 Poruthams of South Indian marriage matching",
"basis": "manual",
"detail": {
"vedha": false
}
}
}

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"
}
}