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

Heliocentric Chart API

Move the observer to the Sun. Instead of the usual Earth-centred sky, this returns the solar system as seen from the Sun — Earth becomes a body, the Moon and the Ascendant drop away, and every planet is given in heliocentric longitude. Pass a moment, get the heliocentric chart. Swiss Ephemeris precision, JSON out.

Endpoint
POST /v1/heliocentric
Cost
20 credits
Latency
~63 ms
Tier
Tier 2
// 01 / What it computes

Heliocentric Chart API

The heliocentric endpoint resolves the supplied date, time, and UTC offset to a Julian day, then asks the Swiss Ephemeris engine for planetary positions referred to the centre of the Sun rather than the Earth. In this frame Earth appears as an orbiting body with its own longitude, while the Moon — which orbits Earth, not the Sun — and the geocentric Ascendant and Midheaven have no meaning and are omitted. The response returns the heliocentric longitudes of the planets and the full aspect grid computed among them, with applying and separating flags and exact orbs. Because heliocentric motion is steady and free of the retrograde loops and parallax that the Earth's own orbit introduces, the planetary spacing reads very differently from a geocentric chart — the positions reflect true orbital geometry around the Sun.

// 02 / Live request

POST/v1/heliocentric

curl -X POST https://api.astroway.info/v1/heliocentric \
  -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": {
    "input": {},
    "planets": [
      {
        "name": "Earth",
        "longitude": 234.2
      },
      {
        "name": "Mars",
        "longitude": 9.1
      }
    ],
    "aspects": [
      {
        "planet1": "Earth",
        "planet2": "Jupiter",
        "type": "trine",
        "orb": 0.9
      }
    ]
  }
}
// 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

Reach for the heliocentric chart in research, financial, and mundane contexts where the Sun-centred view is the analytical standard — market-timing models that track heliocentric planetary angles, mundane studies of planetary cycles, or any analysis that wants orbital geometry without the distortions of geocentric retrogradation. It is also useful as a contrasting overlay to a conventional chart, since a planet that looks retrograde from Earth is simply moving forward around the Sun here. Because there is no Moon, no Ascendant, and no houses in the geocentric sense, treat the output as a planetary-longitude-and-aspect dataset rather than a personal natal chart — it answers questions about cycles and configurations, not about an individual's rising sign.

// 05 / Notes

Notes

This is a Sun-centred frame: Earth is returned as a body, and the Moon, geocentric Ascendant, and Midheaven are absent by construction. Retrograde motion disappears because it is an artifact of viewing from a moving Earth. The output is best read as heliocentric longitudes plus their aspect grid for cycle and mundane work, not as a personal chart. Tropical longitudes and Swiss Ephemeris throughout.

Try the Heliocentric Chart API

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

99.9% SLA · paid plans · 30d status →