POST · VEDIC

KP Horary (Prashna)

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

Returns a KP horary chart from a number 1–249. The number selects one of the 249 Vimshottari-proportional sub-divisions of the zodiac (243 subs plus the 6 split at sign boundaries); the horary ascendant is the start of that sub, and the full Placidus cusp wheel is solved for that ascendant at the moment and place of judgment — both behaviours verified against professional reference software. Planets are placed for the query time with full KP chains.

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: am_live_xxxxxxxxxxxx
BearerAuthorization: Bearer am_live_xxxxxxxxxxxx
Query?api_key=am_live_xxxxxxxxxxxx

Request body

FieldTypeRequiredDescription
namestringNoEchoed in the response.
yearintegerYesYear.
monthintegerYesMonth, 1–12.
dayintegerYesDay of month.
hourintegerYesHour, 24-hour.
minuteintegerYesMinute.
secondintegerNoDefault 0.
latitudenumberYesDecimal degrees.
longitudenumberYesDecimal degrees.
timezonestringYesIANA timezone.
ayanamsastringNoDefault kp_old (Krishnamurti). Any supported ayanamsa accepted.
node_typestringNomean (default, per classical KP ephemeris practice) or true.
horary_numberintegerYes1–249, the querent’s number.

Response shape

FieldTypeDescription
horary_numberintegerEchoed number.
ascendantobjectThe number’s ascendant with full KP chain.
house_cuspsobject/arrayPlacidus cusps from the horary ascendant, each with sub lord.
planets[]arrayQuery-time planets with KP chains and cusp-to-cusp house placement.

Worked example

Number 120 yields ascendant Virgo 22°40'00" (Hasta, Sun sub) regardless of time; the cusps then follow Placidus for the moment and latitude of judgment.

Errors

HTTPCodeCause
400MISSING_FIELDRequired field 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