Vedic

Compatibility: Dashakoota (10-fold 39-point)

Changed on

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.

post/vedic/compatibility/dashakoota

Request

  • Base URL: https://api.astroway.info/v1
  • URL: https://api.astroway.info/v1/vedic/compatibility/dashakoota
  • Auth: API key in header X-Api-Key

Query parameters

fieldsstring

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.

precisioninteger

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.

Request body

Example request

{
  "chart1": {
    "timezone": "Europe/Kyiv"
  },
  "chart2": {
    "timezone": "Europe/Kyiv"
  }
}

Response

Successful calculation

okboolean

Example response

{
  "ok": true
}

Changes

  • ec98fcd88094Revision changes
    • warning

      changed the pattern of the request property / from ^\d{2}:\d{2}:\d{2}$ to ^\d{2}:\d{2}(:\d{2})?$

    • warning

      changed the pattern of the request property / from ^\d{2}:\d{2}:\d{2}$ to ^\d{2}:\d{2}(:\d{2})?$

  • b64222844186Revision changes
    • info

      added the new optional query request parameter fields

    • info

      added the new optional query request parameter precision