Synastry House Overlay

POST

/synastry/house-overlay

request.sh

curl -X POST https://api.astroway.info/v1/synastry/house-overlay \
  -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 } }'

▸ Спробувати POST /synastry/house-overlay

• Production

Locate each chart’s personal planets in the partner’s houses; reports top-3 emphasized houses on either side.

Authorizations

• ApiKeyAuth

Parameters

Query Parameters

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

Request Body ^required

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

Responses

200

Successful calculation

Media type application/json

object

ok

boolean

data

object

chart1InChart2

Array<object>

nullable

object

planetId

number

nullable

planet

string

nullable

longitude

number

nullable

house

number

nullable

chart2InChart1

Array<object>

nullable

object

planetId

number

nullable

planet

string

nullable

longitude

number

nullable

house

number

nullable

emphasizedHouses

object

chart1

Array<number>

nullable

chart2

Array<number>

nullable

Example

{
  "ok": true,
  "data": {
    "chart1InChart2": [
      {
        "planetId": 0,
        "planet": "Sun",
        "longitude": 54.37601980167181,
        "house": 6
      }
    ],
    "chart2InChart1": [
      {
        "planetId": 0,
        "planet": "Sun",
        "longitude": 220.77033612885523,
        "house": 2
      }
    ],
    "emphasizedHouses": {
      "chart1": [
        2
      ],
      "chart2": [
        2
      ]
    }
  }
}

400

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

401

Missing or invalid API key

Media type application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_API_KEY",
    "message": "Invalid API key"
  }
}