Synastry score and cross-aspects (public, no key)
curl -X POST 'https://api.astroway.info/v1/public/synastry' \ -H 'Content-Type: application/json' \ -d '{"chart1":{"date":"1990-07-14","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52},"chart2":{"date":"1992-03-22","time":"09:15:00","timezoneOffset":2,"latitude":48.85,"longitude":2.35}}'Compatibility score and the planet-to-planet aspect grid for two birth charts, served anonymously. Aspects come back sorted by orb, tightest first, so taking the first six gives the six an embed would show. applying is true when the aspect is still closing. spheres splits the same score by area of life: each sphere is the subset of cross-aspects that touch its body (identity: Sun, emotional: Moon, communication: Mercury, love: Venus, passion: Mars, commitment: Saturn), scored by the same model as score. An aspect between two sphere bodies counts in both. A sphere with no aspect has score: null and count: 0, not 50. The six keys are a closed list; new ones may be added, existing ones are not renamed. strength (0-100) is the weight the score is summed from (aspect type, the two bodies, orb), over its ceiling, an exact Sun-Moon conjunction; tone is the side of the score it lands on, harmonious or challenging, by the same rule (Venus-Mars counts as harmonious in any aspect). chart1 and chart2 are the two natal charts in the shape of POST /public/chart, so houses of one partner can be read against the other without two more calls; a partner with timeUnknown: true has no houses or angles. What stays behind a key: the per-aspect interpretations, the house overlay, composite and Davison charts, all of which the authed POST /synastry returns. Either partner may set timeUnknown: true; cross-aspects survive an unknown time because they are planet to planet. This call costs 3 units of the public rate-limit bucket rather than 1, because it computes two charts and the full matrix: 10 an hour on an undeclared address, 100 per declared site, 200 per address. The response carries X-RateLimit-Cost: 3. localized (follows ?lang= / Accept-Language) carries display names beside the English identifiers, which stay as they are: label translated, labels and spheres as lookup tables keyed by the identifiers, aspects and planets keyed exactly as the aspects rows spell them.
Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ”BCP-47 language (e.g. uk, en, de). Set it once on your HTTP client as its default; for a single call, ?lang= overrides it. Unknown or inactive codes fall back to uk.
Query Parameters
Section titled “Query Parameters ”Example
enLanguage for this call, overriding Accept-Language. The canonical per-call form: a page that renders in one language passes it here rather than reconfiguring its client. Unknown or inactive codes fall back to uk.
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.longitudeRound 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
4Request Body required
Section titled “Request Body required ”Pair of natal charts where either birth time may be unknown. A chart with timeUnknown: true contributes planets and cross-aspects but no houses, angles or overlays.
object
Birth data where the clock time may be unknown. Either pass time (HH:mm:ss), or set timeUnknown: true and omit it. In the second case the response carries planets and aspects but no houses, angles or sect.
object
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.
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.
Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
Birth data where the clock time may be unknown. Either pass time (HH:mm:ss), or set timeUnknown: true and omit it. In the second case the response carries planets and aspects but no houses, angles or sect.
object
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.
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.
Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
Example
{ "chart1": { "date": "1990-07-14", "time": "14:30:00", "timezoneOffset": 3, "latitude": 50.45, "longitude": 30.52 }, "chart2": { "date": "1992-03-22", "time": "09:15:00", "timezoneOffset": 2, "latitude": 48.85, "longitude": 2.35 }}Responses
Section titled “ Responses ”OK
object
object
object
object
object
object
object
object
object
Free-tier watermark, present on every public response. Keys on a paid plan do not receive it.
Example
{ "ok": true, "data": { "score": 59, "label": "balanced", "aspects": [ { "planetA": "Pluto", "planetB": "Saturn", "aspect": "Square", "orb": 0.0509, "applying": false, "strength": 24, "tone": "challenging" }, { "planetA": "Uranus", "planetB": "Jupiter", "aspect": "Trine", "orb": 0.0787, "applying": true, "strength": 22, "tone": "harmonious" }, { "planetA": "Chiron", "planetB": "Neptune", "aspect": "Opposition", "orb": 0.3942, "applying": false, "strength": 19, "tone": "challenging" } ], "count": 45, "spheres": [ { "key": "identity", "score": 67, "label": "harmonious", "count": 8 }, { "key": "emotional", "score": 72, "label": "harmonious", "count": 9 }, { "key": "communication", "score": 68, "label": "harmonious", "count": 8 }, { "key": "love", "score": 68, "label": "harmonious", "count": 4 }, { "key": "passion", "score": 56, "label": "balanced", "count": 4 }, { "key": "commitment", "score": 43, "label": "mixed", "count": 5 } ], "localized": { "label": "Збалансована", "labels": { "harmonious": "Гармонійна", "balanced": "Збалансована", "mixed": "Змішана", "challenging": "Напружена" }, "spheres": { "identity": "Особистість", "emotional": "Емоції", "communication": "Спілкування", "love": "Кохання", "passion": "Пристрасть", "commitment": "Зобов’язання" }, "aspects": { "Square": "Квадратура", "Trine": "Трин", "Opposition": "Опозиція" }, "planets": { "Pluto": "Плутон", "Saturn": "Сатурн", "Uranus": "Уран", "Jupiter": "Юпітер", "Chiron": "Хірон", "Neptune": "Нептун" } } }, "_footer": "Powered by astroway.api - get your own key at https://api.astroway.info"}Invalid input
Example
{ "ok": false, "error": { "code": "INVALID_FIELD", "message": "Unsupported fields: \"tz\", \"lat\", \"lng\". Rename them to \"timezoneOffset\", \"latitude\", \"longitude\". See details for what each one expects.", "details": [ { "path": "tz", "expected": "timezoneOffset", "message": "numeric hours from UTC, e.g. 5.75; a zone name goes in timezone" }, { "path": "lat", "expected": "latitude", "message": "decimal degrees, north positive" }, { "path": "lng", "expected": "longitude", "message": "decimal degrees, east positive" } ], "docs": "https://api.astroway.info/en/errors/#invalid_field" }}