Synastry score and cross-aspects (public, no key)
Changed onCompatibility 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.
Request
- Base URL: https://api.astroway.info/v1
- URL: https://api.astroway.info/v1/public/synastry
- Auth: none required
Query parameters
Language 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.
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.
Headers
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.
Request body
Example request
{
"chart1": {
"timezone": "Europe/Kyiv"
},
"chart2": {
"timezone": "Europe/Kyiv"
}
}Response
OK
Example response
{
"ok": true,
"_footer": "Powered by astroway.api - get your own key at https://api.astroway.info"
}Changes
- warning
changed the pattern of the request property
/from^\d{2}:\d{2}:\d{2}$to^\d{2}:\d{2}(:\d{2})?$ - warning
changed the pattern of the request property
/from^\d{2}:\d{2}:\d{2}$to^\d{2}:\d{2}(:\d{2})?$ - info
added the optional property
///to the response with the status - info
added the optional property
///to the response with the status
- warning
- info
added the new optional
headerrequest parameterAccept-Language - info
added the new optional
queryrequest parameterlang - info
added the optional property
/to the response with the status
- info