AstroWay/api v2.95.1 · astrology-api
all systems operational
// astrology api · POST /v1/astrocartography

Astrocartography API

Astrocartography takes a single birth moment and projects it onto the whole planet: instead of asking where the planets were in the sky, it asks where on Earth each planet was angular. The endpoint returns the line geometry you plot on a world map to see which longitudes activate which planetary energy.

Endpoint
POST /v1/astrocartography
Cost
50 credits
Latency
~76 ms
Tier
Tier 3
// 01 / What it computes

Astrocartography API

From the birth date, clock time, UTC offset, and birth coordinates, the endpoint fixes the exact sky for that instant, then sweeps the globe to find every meridian and curve where a planet stood on one of the four angles. For each of the ten planets plus the nodes it traces four families of line: the rising line where the body was on the Ascendant, the setting line on the Descendant, the culminating line on the Midheaven, and the anti-culminating line on the Imum Coeli. The MC and IC lines run as clean meridians; the AC and DC lines bend as latitude-dependent curves, since a body that rises due east at one latitude rises far to the north or south at another. Everything is returned as serialisable line geometry under data.lines, ready to feed straight into a mapping library. This is the relocational technique popularised by Jim Lewis as Astro*Carto*Graphy.

// 02 / Live request

POST/v1/astrocartography

curl -X POST https://api.astroway.info/v1/astrocartography \
  -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": {
    "lines": [
      {
        "planet": "Venus",
        "type": "MC",
        "longitude": 14.2
      },
      {
        "planet": "Jupiter",
        "type": "AC",
        "points": [
          "…"
        ]
      }
    ]
  }
}
// 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 location is the variable and you want to know how a chart re-expresses itself across the map — for relocation advice, travel and where-to-live tools, or any feature that overlays a person's chart on a globe. It is the natural backend for an interactive map: request the lines once for a birth moment, render them as polylines, and let the user pan across continents to read which planet governs which corridor. Because the output is pure geometry rather than prose, it composes cleanly with your own front-end styling, clustering, and click-to-interpret layers. Pair it with the natal-chart call when you want both the home-chart structure and the relocated lines side by side; the two share the same birth resolution, so the planetary positions behind the map agree exactly.

// 05 / Notes

Notes

Positions come from the Swiss Ephemeris (Astrodienst) compiled to WASM, the same engine behind the natal endpoints, so the lines anchor to the identical planetary longitudes. Angularity is computed in the tropical zodiac. The response carries geometry only — drawing, projection, and styling of the world map are left to your client.

Try the Astrocartography API

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

99.9% SLA · paid plans · 30d status →