TRANSIT API

Transits

Overview

The Transit API gives you real-time and historical planetary positions, aspects, dignity, sign ingress, retrograde windows, combustion, nakshatra transits, moon phases, eclipses, and a merged upcoming-events timeline — all computed from the Swiss Ephemeris.

Endpoints are split into Vedic (sidereal, Lahiri default) and Western (tropical) namespaces. Both share the same core architecture but differ in zodiac frame, aspect model, and available analytical fields.

Vedic Transit endpoints

Snapshot (current sky)

EndpointDescription
basicLean 9-planet positions: sign, nakshatra, house, retrograde. Defaults to “now”.
advancedAdds dignity, combustion distance, baladi avastha, nakshatra lord & percent, sign element.
extendedFull payload: Sanskrit names, navamsa, vargottama, plus 4 outer planets (position-only).
aspectsParashari graha drishti between transiting planets (sign-based, classical).
chartsSigned chart-image URLs for D1 (Rasi) and D9 (Navamsa), North and South Indian styles.

Calendar events

EndpointDescription
nakshatraNakshatra transit windows per planet.
ingressSign ingress events — when planets enter/leave signs.
retrogradeRetrograde/direct station windows with motion filter.
combustCombustion windows — planets too close to the Sun.
moon-phasesSidereal lunar phases with cycle grouping and phase filtering.
eclipsesSolar & lunar eclipses (sidereal sign + nakshatra positions).
ephemerisDaily sidereal positions for a month (00:00 UTC), both true & mean nodes.

Hybrid

EndpointDescription
natal-transit-aspectsDegree-orb aspects between transiting and natal planets over a date range.
upcomingMerged chronological timeline: ingress, retrograde, combust, nakshatra, eclipses, panchang.

Western Transit endpoints

The Western namespace mirrors the Vedic structure but uses the tropical zodiac. See the Western Transit overview.

KP Transit

KP-specific transit data (ruling planets, transit cusps) is available at /api/v3/transit/kp/planets.

Common parameters

All transit endpoints accept POST with Content-Type: application/json. Authentication is via X-Api-Key header (recommended), Authorization: Bearer, or query-string ?api_key=.

Snapshot endpoints

FieldTypeRequiredDescription
latitudenumberYesObserver latitude (−90…90).
longitudenumberYesObserver longitude (−180…180).
timezonestringYesIANA timezone (e.g. Asia/Kolkata).
yearintegerNoDefaults to current year.
monthintegerNoDefaults to current month.
dayintegerNoDefaults to current day.
hourintegerNo24-hour clock. Defaults to current hour.
minuteintegerNoDefaults to current minute.
secondintegerNoDefault 0.
ayanamsastringNoDefault lahiri. Full list →
node_typestringNomean (default) or true.

Query types (calendar endpoints)

Calendar endpoints (nakshatra, ingress, retrograde, combust, moon-phases) share a query_type parameter:

query_typeRequired fieldsDescription
currenttimezoneCurrently active event(s).
datedate (YYYY-MM-DD)Events on a specific date.
rangefrom_date, to_dateEvents within a date range.
monthmonth, yearAll events in a calendar month.
yearyearAll events in a calendar year.