Transit Chart API
Snapshot the sky on any target date and lay it over a person's natal house frame in one POST. Transiting planets, the natal cusps they fall into, the aspect grid among the transiting bodies, plus parallels and antiscia — Swiss Ephemeris precision, JSON out.
Transit Chart API
The transits endpoint takes a person's natal data — birth date, time, UTC offset, latitude, longitude, and house system — and a separate target moment. It resolves that target date and clock time to a Julian day, asks the Swiss Ephemeris engine for the geocentric longitude, latitude, and speed of every transiting body, then casts those positions into the houses derived from the natal location. The response carries the transiting planets with their signs and house placements, the natal house cusps, and the full aspect grid computed among the transiting bodies themselves, each with applying or separating flags and exact orbs. It also returns parallel and antiscia (mirror-point) aspects for declination and solstitial-axis work. Retrograde motion is flagged from body speed, so you can see which transits are direct, stationary, or moving backward at the requested moment.
POST/v1/transits
curl -X POST https://api.astroway.info/v1/transits \
-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,
"transitDate": "2026-06-15",
"transitTime": "12:00:00",
"transitTzOffset": 3
}'{
"ok": true,
"data": {
"input": {},
"julianDay": 2461206.875,
"planets": [
{
"name": "Sun",
"longitude": 84.29,
"sign": "Gemini",
"house": 11
}
],
"houses": {
"ascendant": 160.4,
"mc": 70.1,
"cusps": [
"…"
]
},
"aspects": [
{
"planet1": "Sun",
"planet2": "Moon",
"type": "conjunction",
"orb": 1.2,
"applying": true
}
],
"parallelAspects": [
"…"
],
"antiscia": [
"…"
]
}
}Parameters
| name | type | Required | |
|---|---|---|---|
| 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). |
| transitDate | string (YYYY-MM-DD) | yes | Required target date for the transit snapshot (YYYY-MM-DD). |
| transitTime | string (HH:MM:SS) | no | Optional clock time of the transit moment (HH:MM:SS). |
| transitTzOffset | number (hours) | no | Optional UTC offset for the transit moment, in hours. |
When to use it
Use this when you want the whole sky as it sits over someone's chart on a given day — a daily-transits widget, a weather-style 'what's overhead now' panel, or the raw frame an AI agent reads before describing the current astrological climate. Because it returns the transit chart over the natal house framework rather than a curated list of transit-to-natal contacts, it is the right call when you need the structural snapshot itself. If instead you want timed transit-to-natal hits scanned across a date range — exact dates, ingresses, station points — reach for the transit-calendar endpoint, which is built for that timing job. Pair the two: this endpoint for the moment-in-time chart, the calendar for the forward-looking event list.
Notes
Be precise about scope: this returns the transit chart laid over the natal house frame, not a pre-filtered transit-to-natal aspect list. The aspect grid is computed among the transiting bodies, not between transit and natal points. For to-natal timing across a span of dates, use /transit-calendar. Houses follow your chosen natal system; tropical zodiac and Swiss Ephemeris throughout.
Try the Transit Chart API
Grab a key and make your first call in under a minute.