LifeAstroAPILifeAstroAPI

API Reference / Vedic Astrology / Chart (Kundli)

GET
10 credits

/v1/chart/nakshatra

Nakshatra, pada and nakshatra lord of all 9 planets.

What this tells you

Returns the nakshatra, pada and nakshatra lord of each of the 9 grahas, by name. The Moon's entry is the Janma Nakshatra, used for dasha start, naming and matching. The Moon-nakshatra attributes used in Ashtakoota (varna, vashya, yoni, gana, nadi) are not here — call /v1/chart/avakhada for those. For nakshatra index numbers instead of names, use `nakshatra_idx` from /v1/chart/planets.

Request

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

example request
curl "https://api.lifeastroapi.com/v1/chart/nakshatra?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.

NameRequiredExampleDescription
dateyes1990-01-15Birth date (YYYY-MM-DD).
tzyesAsia/KolkataBirth place timezone: IANA name (Asia/Kolkata) or UTC offset (+05:30).
latyes19.076Birth place latitude in decimal degrees.
lonyes72.8777Birth place longitude in decimal degrees.
timeno10:30Birth time (HH:MM, 24-hour, local). Defaults to 12:00.
ayanamsano—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",
  "planets": [
    {
      "planet": "Sun",
      "nakshatra": "Uttara Ashadha",
      "pada": 2,
      "lord": "Sun"
    },
    {
      "planet": "Moon",
      "nakshatra": "Purva Phalguni",
      "pada": 3,
      "lord": "Venus"
    }
  ]
}

Field reference

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

FieldTypeMeaning
datestring
Birth date you sent (YYYY-MM-DD), echoed back.
example: "1990-01-15"
timestring
Birth time you sent, echoed back. "12:00" when you leave `time` out.
example: "10:30"
tzstring
Timezone you sent (IANA name or fixed offset such as +05:30), echoed back.
example: "Asia/Kolkata"
locationobject
Birth coordinates used. `alt` is in metres and is 0 unless you send `alt`.
example: { "lat": 19.076, "lon": 72.8777, "alt": 0 }
ayanamsastring
Ayanamsa used. Default lahiri; set it with the `ayanamsa` parameter (lahiri, raman, krishnamurti, fagan, yukteshwar, true_chitrapaksha).
example: "lahiri"
ayanamsa_valuenumber
Ayanamsa in degrees at the birth moment. Sidereal longitude = tropical longitude − this value.
example: 23.71795
house_systemstring
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"
planets[]array of 9 objects
One entry per graha, always in the order Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu.
example: [{ "planet": "Sun", … }, …]
planets[].planetstring
Planet name. Translated with `locale`.
example: "Sun"
planets[].nakshatrastring
Name of the nakshatra the planet is in. Translated with `locale`.
example: "Uttara Ashadha"
Jyotish: The Moon's nakshatra is the Janma Nakshatra — the single most important nakshatra for the native.
planets[].padainteger (1–4)
Quarter (pada) within the nakshatra.
example: 2
planets[].lordstring
Vimshottari lord of the nakshatra. Translated with `locale`.
example: "Sun"
Jyotish: The lord of the Moon's nakshatra rules the first Vimshottari mahadasha.

Usage tips

How to use it

  • Find the Janma Nakshatra
    The order of planets never changes, so the Moon is always `planets[1]`. This also works when `locale` translates the planet names.
  • Cache forever
    Birth-fixed. Hash birth details and cache indefinitely.

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.