# Zodiac sign pair relations (public, no key)

`GET https://api.astroway.info/v1/public/compatibility/matrix`

All 78 unordered pairs of zodiac signs (each sign with itself included), each with the classical whole-sign relation: `same`, `sextile`, `square`, `trine`, `opposition`, or `aversion` for signs one or five apart, which classically do not see each other. `tone` follows Ptolemy (Tetrabiblos I.13): trine, sextile and same sign are `harmonious`, square and opposition `challenging`, aversion `neutral`. There is deliberately no 0-100 score: a pair of signs has no orb and no bodies for the synastry model to weigh, so any number would be invented. For a score, send two birth charts to POST /public/synastry. Static data, `Cache-Control: public, max-age=604800`.

Group: Public. Auth: none, this endpoint answers without a key.

## Parameters

| Name | In | Required | Type | Description |
|---|---|---|---|---|
| `fields` | query | no | 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. |
| `precision` | query | no | integer | 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. |

## Responses

| Status | Meaning |
|---|---|
| 200 | OK |
| 400 | Invalid sign or date |

### Success fields, under `data`

| Field | Type | Required | Description |
|---|---|---|---|
| `pairs` | object[] | no |  |
| `count` | number | no |  |

## Example

```bash
curl 'https://api.astroway.info/v1/public/compatibility/matrix'
```

---

Rendered from https://api.astroway.info/v1/openapi.json. HTML page: https://api.astroway.info/docs/api/operations/publiccompatibilitymatrix/