AstroWay/api v2.95.1 · hi
सभी सिस्टम सामान्य हैं
// astrology api · POST /v1/parallel-aspects

Declination Aspects API

Most aspect work happens along the ecliptic in longitude, but two bodies can also relate by declination — their distance north or south of the celestial equator. This endpoint works in that second dimension, finding parallels and contraparallels, the declination analogues of the conjunction and opposition, and noting when a body runs out of bounds.

Endpoint
POST /v1/parallel-aspects
Cost
20 credits
Latency
~64 ms
Tier
Tier 2
// 01 / What it computes

Declination Aspects API

From the birth date, time, UTC offset, and coordinates the endpoint computes each body's declination — how far north or south of the celestial equator it sits, off the ecliptic plane that longitude is measured on — and then compares those declinations across bodies. Where two bodies share the same declination on the same side of the equator it records a parallel, the declination counterpart of a conjunction; where they share the same declination on opposite sides it records a contraparallel, the counterpart of an opposition. Each contact is returned under data.parallels with the bodies involved. The endpoint also surfaces out-of-bounds context — when a body's declination exceeds the Sun's maximum, carrying it beyond the band the Sun ever reaches, a condition traditionally read as the planet operating without its usual restraint. This gives you a layer of contact that pure longitude misses entirely: two planets with no longitudinal aspect can still be locked in a tight parallel.

// 02 / Live request

POST/v1/parallel-aspects

curl -X POST https://api.astroway.info/v1/parallel-aspects \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "date": "1990-05-15",
  "time": "14:30:00",
  "timezoneOffset": 3,
  "latitude": 50.45,
  "longitude": 30.52
}'
Response (excerpt)
{
  "ok": true,
  "data": {
    "parallels": [
      {
        "planet1": "Sun",
        "planet2": "Moon",
        "type": "contra-parallel",
        "orb": 0.49
      }
    ]
  }
}
// 03 / Parameters

Parameters

nametypeRequired
date string (YYYY-MM-DD) yes Birth date.
time string (HH:MM:SS) yes Local clock time at birth.
timezoneOffset number (hours) yes UTC offset in effect at the birth moment (e.g. 3 for Kyiv summer time). Decimal allowed for half-hour zones.
latitude number yes Birth-place latitude, decimal degrees (north positive).
longitude number yes Birth-place longitude, decimal degrees (east positive).
// 04 / When to use it

When to use it

Use this endpoint when an aspect engine should not stop at the ecliptic — a serious chart analyser, a synastry or transit tool that wants the declination layer, or a report that explains why two planets feel linked despite forming no longitude aspect. Parallels and contraparallels are exactly the contacts a longitude-only grid drops, so adding them fills a real gap rather than duplicating the natal-chart aspect output. The out-of-bounds flag is independently useful: it marks planets the tradition treats as running unchecked, which makes a clean highlight in a chart report. Send the same birth data you used elsewhere and the declination contacts will refer to the same bodies as your longitude aspects, letting you present both grids as two readings of one chart.

// 05 / Notes

Notes

Parallels and contraparallels follow the traditional declination doctrine, treating equal-declination contacts as the analogues of conjunction and opposition; the out-of-bounds reading draws on the work of Kt Boehrer. Declinations are computed by the Swiss Ephemeris (Astrodienst) WASM engine in the tropical frame, on the same bodies as the longitude-based natal endpoints.

Try the Declination Aspects API

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

99.9% SLA · पेड प्लान · 30 दिन स्थिति →