/api/astro/astrocartography/lines/1 creditAstrocartography lines
Every astrocartography line for a birth moment, as coordinates ready to plot on a map. Relocation astrology asks a geographic question rather than a chart one: not where a planet was in the sky, but which places on Earth had it rising, setting, culminating or at the nadir at the moment of birth. Those four curves per planet, drawn on a world map, are the ACG map. For each of twelve bodies you get four lines. The MC and IC lines are meridians, so each is a single longitude. The AC and DC lines are curves, returned as a list of latitude/longitude points you can feed straight into a polyline — every five degrees of latitude by default, adjustable with latitude_step. Curves stop where the body becomes circumpolar, and that is real rather than missing data: above a certain latitude the body never crosses the horizon at all, so there is no rising line to draw there. The cut-off differs per planet because it depends on the declination. latitude and longitude are optional on this endpoint alone. An ACG line is fixed by the birth MOMENT — the formulas use right ascension, declination and sidereal time and nothing else — so requiring a birthplace would imply it changes the answer when it does not. Use /api/astro/astrocartography/relocate/ when you want the lines near a particular place.
https://api.occultapi.com/api/astro/astrocartography/lines/Authentication
Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.
X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/jsonRequest fields
| Field | Type | Required | Notes |
|---|---|---|---|
| date_time | string (date-time) | required | The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers. |
| timezone_as_float | number (double) | required | UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30), -5 for New York in winter, 5.75 for Nepal. This is NOT validated against date_time - if the two disagree you get a successful response for the wrong moment, so derive both from the same source. Use the offset in force on that date, not today's: a summer birth in a country with daylight saving needs the summer offset. min -12 · max 14 |
| bodies | array | optional | Defaults to all twelve. Narrow it to keep responses small. |
| close_curves | boolean | optional | Add points that carry each AC/DC curve to where it ends: the latitude where the body stops rising and setting, at which the AC and DC curves meet on its MC or IC line. Turn on for drawing; off (the default) keeps the plain evenly spaced samples. |
| keys | array | optional | Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls. |
| latitude | number (double) | optional | Latitude of the place, in decimal degrees. Positive is north, negative is south. Example: 26.9124 for Jaipur, 40.7128 for New York. Minutes and seconds are not accepted - convert first. |
| latitude_step | number (double) | optional | Degrees of latitude between points on the AC/DC curves. min 1 · max 15 |
| longitude | number (double) | optional | Longitude of the place, in decimal degrees. Positive is east, negative is west. Example: 75.7873 for Jaipur, -74.0060 for New York. Note the sign: a missing minus puts New York in China. |
| node | string | optional | Which lunar node `north_node` is: true (the default) or mean. truemean |
| projection | string | optional | mundo (the default): true positions, latitude included. zodiac: positions projected onto the ecliptic, matching a relocated chart 1:1. mundozodiac |
Example request
This example is not yet verified
The field names and types below are taken from the API definition and are accurate, but this particular body has not returned a success when we last ran it — it may need a value we cannot infer. Treat it as a starting point rather than a working command.
curl -X POST https://api.occultapi.com/api/astro/astrocartography/lines/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"2026-09-01 06:00:00","timezone_as_float":5.5,"latitude":26.9124,"longitude":75.7873,"node":"true","projection":"mundo"}'Response
A verified example response is not available for this endpoint yet. The request shape above is generated from the API definition and is accurate; we publish response samples only once we have proven them against a live call.
Errors
Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.