POST · VEDIC

KP Transit Planets

Endpoint POST https://starsapi.com/api/v3/vedic/kp/transit

Returns the full KP transit snapshot for any moment — all nine planets with sign, house placement (Placidus), nakshatra with pada, and the complete KP lord chain (sign lord, star lord, sub lord, sub-sub lord), plus daily motion, retrograde and combustion flags. The ascendant carries the same lord chain.

Date and time are optional — omit them entirely and the current moment at the given location is used, making this a one-call "sky right now" endpoint for KP work.

All KP endpoints default to the KP Old (Krishnamurti) ayanamsa and mean nodes, matching classical KP ephemeris practice. Both are overridable per request.

Authentication

MethodExample
Header (recommended)X-Api-Key: sa_live_xxxxxxxxxxxx
BearerAuthorization: Bearer sa_live_xxxxxxxxxxxx
Query?api_key=sa_live_xxxxxxxxxxxx

Request body

FieldTypeRequiredDescription
latitudenumberYesDecimal degrees.
longitudenumberYesDecimal degrees.
timezonestringYesIANA timezone.
yearintegerNoDefaults to the current moment when date/time fields are omitted.
monthintegerNoMonth, 1–12.
dayintegerNoDay of month.
hourintegerNoHour, 24-hour.
minuteintegerNoMinute.
secondintegerNoDefaults to 0 when any date/time field is supplied; only when all date/time fields are omitted does it follow the current clock.
placestringNoEchoed in moment.place.
ayanamsastringNoDefault kp_old (Krishnamurti). Any supported ayanamsa accepted.
node_typestringNomean (default, per classical KP ephemeris practice) or true.

Response shape

FieldTypeDescription
momentobjectThe moment used — date, time, timezone, place.
zodiac / systemstringAlways sidereal / kp.
house_systemstringPlacidus (KP standard).
ascendantobjectLongitude (decimal + DMS), degree_in_sign, sign with lord, nakshatra with lord and pada, sub_lord, sub_sub_lord.
planetsobjectKeyed by planet name (Sun…Ketu). Each carries the same positional and KP-lord fields as the ascendant, plus house (Placidus placement), daily_motion, is_retrograde, is_combust.

Errors

HTTPCodeCause
400MISSING_FIELDtimezone, latitude or longitude absent.
400INVALID_DATEBad calendar date.
400INVALID_TIMEHour/minute/second out of range.
400INVALID_TIMEZONENon-IANA timezone.
400INVALID_COORDINATELat/lon out of range.
400INVALID_PARAMBad ayanamsa, node_type, or other option.
405METHOD_NOT_ALLOWEDNon-POST request.

See also