Parans API

The endpoint resolves the birth moment to a Julian day, computes the full astrocartography set (four angular lines per body), and then intersects every line with every line belonging to a different planet. Each intersection is returned with both parent planets, both line types, and the latitude and longitude where the crossing falls. Because MC and IC lines are meridians and AC and DC lines are latitude-dependent curves, most crossings are geometric rather than symmetrical: a Sun-MC and Moon-ASC pair meets at exactly one place per hemisphere, not on a shared band. A typical chart yields somewhere over four hundred crossings across the globe, which is why they are returned as a flat, sortable list rather than pre-filtered by any notion of importance.

curl -X POST https://api.astroway.info/v1/parans \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
  "date": "1990-05-15",
  "time": "14:30:00",
  "timezoneOffset": 3
}'

{
  "ok": true,
  "data": {
    "count": 414,
    "parans": [
      {
        "planet1Id": 0,
        "planet1Name": "Sun",
        "line1Type": "MC",
        "planet2Id": 1,
        "planet2Name": "Moon",
        "line2Type": "ASC",
        "location": { "lat": -45.9153, "lng": 6.5735 }
      }
    ]
  }
}

Reach for parans when astrocartography lines alone are too coarse. Lines tell a user that a corridor carries Jupiter; parans tell them that at one specific spot on that corridor Jupiter meets Venus. That distinction is what relocation consultants charge for, and it is the layer most map tools skip. Practically: render the lines as polylines and the parans as clickable markers, or filter the list to the planet pairs your product cares about and rank nearby cities by proximity to those points. The response is coordinates only, so you can join it against your own city or region dataset without fighting a prose format. Note that this endpoint needs no birth place, only the moment, since the crossings are properties of the sky rather than of where the person happened to be.

Positions come from the Swiss Ephemeris (Astrodienst) compiled to WASM, the same engine as the natal endpoints, so parans anchor to the same planetary longitudes as the lines they derive from. Crossings are computed in the tropical zodiac from the full line geometry rather than from a latitude approximation. Classical paran doctrine as set out by Bernadette Brady also treats star-to-planet parans within a shared latitude band; this endpoint covers the planet-to-planet case that the astrocartography map itself generates.