AstroWay/api v2.95.1 · ko
모든 시스템 정상 작동 중
// astrology api · POST /v1/composite

Composite Chart API

Fuse two birth charts into one. The midpoint composite takes every planetary pair and the two sets of angles, finds the midpoint of each, and returns a single derived chart that models the relationship as its own entity. Two charts in, one composite out, JSON.

Endpoint
POST /v1/composite
Cost
50 credits
Latency
~62 ms
Tier
Tier 3
// 01 / What it computes

Composite Chart API

The composite endpoint accepts two full natal charts and constructs a third chart from their midpoints. For each body it pairs the two longitudes and computes the midpoint along the shorter arc, doing the same for the two Ascendants and the two Midheavens, so the composite carries its own angles and house framework rather than borrowing either partner's. From those midpoint positions it assigns signs and houses and computes the complete internal aspect grid with applying and separating flags and exact orbs. The result is not a comparison of two people but a portrait of the bond itself — where the relationship's Sun, Moon, and angles land, which aspects structure it, and how its energies distribute across the houses. Each partner chart is supplied in the same shape as a standard natal chart, so you can compute the two natals first and feed them straight in.

// 02 / Live request

POST/v1/composite

curl -X POST https://api.astroway.info/v1/composite \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "chart1": {
    "date": "1990-05-15",
    "time": "14:30:00",
    "timezoneOffset": 3,
    "latitude": 50.45,
    "longitude": 30.52
  },
  "chart2": {
    "date": "1985-11-03",
    "time": "08:15:00",
    "timezoneOffset": 2,
    "latitude": 48.46,
    "longitude": 35.04
  }
}'
Response (excerpt)
{
  "ok": true,
  "data": {
    "input": {},
    "planets": [
      {
        "name": "Sun",
        "longitude": 117.3,
        "sign": "Cancer",
        "house": 7
      }
    ],
    "houses": {
      "ascendant": 12.4,
      "mc": 280,
      "cusps": [
        "…"
      ]
    },
    "aspects": [
      {
        "planet1": "Sun",
        "planet2": "Venus",
        "type": "sextile",
        "orb": 0.6
      }
    ]
  }
}
// 03 / Parameters

Parameters

nametypeRequired
chart1 object yes First partner's birth data as an object with the same shape as a natal chart.
chart2 object yes Second partner's birth data as an object with the same shape as a natal chart.
// 04 / When to use it

When to use it

Reach for the composite when the unit of interest is the relationship, not the individuals — a couple's-chart feature, a 'chemistry of the pair' report, or an AI flow that needs the relationship modelled as a single subject before it interprets. It complements synastry: synastry overlays one person's planets on the other's to show how they touch, while the composite collapses both into one derived chart to show what the relationship is in its own right. Use it for romantic pairings, business partnerships, or any two-party bond where a unified chart reads more cleanly than a cross-aspect grid. If you specifically want the time-space midpoint method — a real chart cast for the midpoint in time and place — use the Davison endpoint instead.

// 05 / Notes

Notes

This is the midpoint composite: every position is the arithmetic midpoint of the corresponding pair, including the angles, so the chart has genuine cusps of its own. It is distinct from the Davison time-space midpoint chart, which is cast for the midpoint moment and location and lives on the separate /davison endpoint. Tropical zodiac and Swiss Ephemeris throughout.

Try the Composite Chart API

Grab a key and make your first call in under a minute.

99.9% SLA · 유료 플랜 · 30일 상태 →