---
title: "Match Score (dating compatibility)"
method: POST
path: "/match/score"
tags: ["Comparisons"]
---

# Match Score (dating compatibility)

`POST /match/score`

One-call dating-compatibility aggregate over the synastry engine: overall score (0-100) + label + harmony/tension, the attraction score (Venus-Mars / Moon-Venus / 5th-house), the most influential cross-aspects, and green/red flags surfaced from those aspects. Built for dating apps that want a single call instead of synastry + attraction + their own flag logic. Same TwoChart input as /synastry.

## Request body

- TwoChart — Pair of natal charts for relationship calculations: synastry, composite, davison.
  - `chart1` ChartInput, required — Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Coordinates are latitude and longitude in decimal degrees, plus timezoneOffset in hours from UTC; the short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD. Omitting the coordinates is not the same as skipping them: houses, angles and everything derived from them are then computed for 0°N 0°E at UTC, which is a wrong answer rather than a neutral default.
    - `date` string, required
    - `time` string, required
    - `timezoneOffset` number, nullable
    - `latitude` number, nullable
    - `longitude` number, nullable
    - `houseSystem` string
    - `name` string
    - `city` string
    - `zodiacType` 'tropical' | 'sidereal'
    - `ayanamsaId` number, nullable
    - `cosmogram` boolean
  - `chart2` ChartInput, required — Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Coordinates are latitude and longitude in decimal degrees, plus timezoneOffset in hours from UTC; the short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD. Omitting the coordinates is not the same as skipping them: houses, angles and everything derived from them are then computed for 0°N 0°E at UTC, which is a wrong answer rather than a neutral default.
    - `date` string, required
    - `time` string, required
    - `timezoneOffset` number, nullable
    - `latitude` number, nullable
    - `longitude` number, nullable
    - `houseSystem` string
    - `name` string
    - `city` string
    - `zodiacType` 'tropical' | 'sidereal'
    - `ayanamsaId` number, nullable
    - `cosmogram` boolean

## Response `200`

Successful calculation

- object
  - `ok` boolean
  - `data` object
    - `score` number, nullable
    - `label` string, nullable
    - `harmony` number, nullable
    - `tension` number, nullable
    - `attraction` object, nullable
      - `score` number, nullable
    - `topAspects` object[], nullable
      - `aspect` string, nullable
      - `type` string, nullable
      - `angle` number, nullable
      - `orb` number, nullable
      - `tone` string, nullable
    - `greenFlags` object[], nullable
      - `aspect` string, nullable
      - `note` string, nullable
    - `redFlags` object[], nullable
      - `aspect` string, nullable
      - `note` string, nullable

## Other responses

- `400` — Validation error
- `401` — Missing or invalid API key

---

[API](https://skmtc.dev/astroway/apis/astroway-calculation-api.md) · [All operations](https://skmtc.dev/astroway/apis/astroway-calculation-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/astroway/astroway-calculation-api/revisions/793e5c2dbcdf/schema)