/v1/chart/kp-sublord

KP system sub-lords.

What this tells you

KP (Krishnamurti Paddhati) divides each nakshatra into 9 unequal subs sized by the Vimshottari dasha years. The sub lord is the finest-grained significator — central to KP and horary work. This endpoint gives the star, sub and sub-sub lord of each of the 9 grahas. KP house cusps (Placidus) with their star, sub and sub-sub lords come from /v1/chart/kp-house-significator.

Request

All requests require an Authorization header with your dv_live_* API key.

example request

curl "https://api.lifeastroapi.com/v1/chart/kp-sublord?date=1990-01-15&tz=Asia%2FKolkata&lat=19.076&lon=72.8777&time=10%3A30" \
  -H "Authorization: Bearer YOUR_API_KEY"

Query parameters

Checked against the API: a parameter is marked required when the request fails without it.

Name	Required	Example	Description
`date`	yes	`1990-01-15`	Birth date (YYYY-MM-DD).
`tz`	yes	`Asia/Kolkata`	Birth place timezone: IANA name (Asia/Kolkata) or UTC offset (+05:30).
`lat`	yes	`19.076`	Birth place latitude in decimal degrees.
`lon`	yes	`72.8777`	Birth place longitude in decimal degrees.
`time`	no	`10:30`	Birth time (HH:MM, 24-hour, local). Defaults to 12:00.
`ayanamsa`	no	—	Ayanamsa (sidereal offset) to use. Defaults to lahiri.

Response (200 OK)

The real response to the example request above, generated from the API itself. Long arrays are trimmed to their first two items. Field names are stable across versions.

200 response

{
  "date": "1990-01-15",
  "time": "10:30",
  "location": {
    "lat": 19.076,
    "lon": 72.8777,
    "alt": 0
  },
  "tz": "Asia/Kolkata",
  "ayanamsa": "lahiri",
  "ayanamsa_value": 23.71795,
  "house_system": "whole_sign",
  "kp": [
    {
      "planet": "Sun",
      "star_lord": "Sun",
      "sub_lord": "Rahu",
      "sub_sub_lord": "Moon"
    },
    {
      "planet": "Moon",
      "star_lord": "Venus",
      "sub_lord": "Jupiter",
      "sub_sub_lord": "Jupiter"
    }
  ]
}

Field reference

Every field in the response, with its type, a real example, and what it means.

Field	Type	Meaning
date	string	Birth date you sent (YYYY-MM-DD), echoed back. example: `"1990-01-15"`
time	string	Birth time you sent, echoed back. "12:00" when you leave `time` out. example: `"10:30"`
tz	string	Timezone you sent (IANA name or fixed offset such as +05:30), echoed back. example: `"Asia/Kolkata"`
location	object	Birth coordinates used. `alt` is in metres and is 0 unless you send `alt`. example: `{ "lat": 19.076, "lon": 72.8777, "alt": 0 }`
ayanamsa	string	Ayanamsa used. Default lahiri; set it with the `ayanamsa` parameter (lahiri, raman, krishnamurti, fagan, yukteshwar, true_chitrapaksha). example: `"lahiri"`
ayanamsa_value	number	Ayanamsa in degrees at the birth moment. Sidereal longitude = tropical longitude − this value. example: `23.71795`
house_system	string	Echo of the optional `house_system` parameter (default whole_sign). This endpoint does not use it, so you never need to send it; only /v1/chart/houses changes with it. example: `"whole_sign"`
kp[]	array of 9 objects	One entry per graha, Sun to Ketu. Planets only — no house cusps. example: `[{ "planet": "Sun", "star_lord": "Sun", … }, …]`
kp[].planet	string	Planet name. Translated with `locale`. example: `"Sun"`
kp[].star_lord	string	Star lord: the Vimshottari lord of the nakshatra the planet is in. example: `"Sun"`
kp[].sub_lord	string	KP sub lord. The nakshatra is split into 9 unequal parts in proportion to the Vimshottari dasha years, starting from the star lord; this is the lord of the part the planet falls in. example: `"Rahu"`
kp[].sub_sub_lord	string	The sub is split again the same way, starting from the sub lord; this is the lord of that finer part. example: `"Moon"`

Usage tips

How to use it

Use the KP ayanamsa
Sub lords change with the ayanamsa. KP practice uses the Krishnamurti ayanamsa, so pass `ayanamsa=krishnamurti`; otherwise Lahiri is used.
KP-specific apps
Only call this endpoint when your app supports KP-style analysis. Traditional Parashari apps should use /v1/chart/planets and /v1/chart/houses instead.

Errors

Every error follows the same envelope. Use the error.code field (not the message) for conditional logic in your integration.

401 Unauthorized

{
  "error": {
    "code": "unauthorized",
    "message": "missing or invalid API key",
    "request_id": "req_01hqy7k8c3e7m1n"
  }
}

402 Payment Required

{
  "error": {
    "code": "trial_exhausted",
    "message": "your free trial credits are exhausted — pick a plan to continue",
    "top_up_url": "https://lifeastroapi.com/pricing",
    "request_id": "req_01hqy7k8c3e7m1n"
  }
}

429 Too Many Requests

{
  "error": {
    "code": "rate_limited",
    "message": "rate limit exceeded; retry after 12 seconds",
    "request_id": "req_01hqy7k8c3e7m1n"
  }
}

Try it

Get a dv_live_* key from your dashboard and paste into the cURL snippet above. New accounts get 1,500 free credits. Sign up.