API Reference / Vedic Astrology / Chart (Kundli)
/v1/chart/planet/{name}
Single planet detail.
What this tells you
Same data as /v1/chart/planets for one planet, wrapped in a `planet` object. Use it when your UI needs only one body (for example "which house is my Moon in?"). Dignity is not included; call /v1/chart/dignity for that.
Request
All requests require an Authorization header with your dv_live_* API key.
curl "https://api.lifeastroapi.com/v1/chart/planet/sun?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.
{
"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",
"planet": {
"id": "sun",
"name": "Sun",
"sidereal_lon": 271.063319,
"sign_index": 9,
"deg_in_sign": 1.063319,
"dms_in_sign": "01°03'47\"",
"house": 12,
"nakshatra_idx": 20,
"pada": 2,
"nak_lord": "Sun",
"speed": 1.018256,
"is_retro": false,
"ecl_lat": -0.000088
}
}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. Planet `house` numbers here are always whole-sign. example: "whole_sign" |
| planet | object | The requested planet. Same fields as one item of `planets[]` in /v1/chart/planets. example: { "id": "sun", "name": "Sun", … } |
| planet.id | string | Stable lowercase English key. It does not change with `locale`, so use it to match planets in code. example: "sun" |
| planet.name | string | Planet name. Translated when you pass `locale` (e.g. `?locale=hi`). example: "Sun" |
| planet.sidereal_lon | number (0–360) | Sidereal longitude in degrees, with the chosen ayanamsa applied. Use this for your own chart math. example: 271.063319 |
| planet.sign_index | integer (0–11) | Sign: 0=Aries, 1=Taurus, …, 11=Pisces. No sign name is returned; map the index yourself. example: 9 |
| planet.deg_in_sign | number (0–30) | Degrees inside the sign. example: 1.063319 |
| planet.dms_in_sign | string | Degrees, minutes and seconds inside the sign, for display. example: "01°03'47\"" |
| planet.house | integer (1–12) | Whole-sign house counted from the ascendant sign. Always whole-sign, even if you pass `house_system`. example: 12 |
| planet.nakshatra_idx | integer (0–26) | Nakshatra: 0=Ashwini, 1=Bharani, …, 26=Revati. example: 20 |
| planet.pada | integer (1–4) | Quarter (pada) of the nakshatra. example: 2 |
| planet.nak_lord | string | Vimshottari lord of the nakshatra. Translated with `locale`. example: "Sun" |
| planet.speed | number | Daily motion in longitude, in degrees per day. Negative means retrograde. example: 1.018256 |
| planet.is_retro | boolean | True when `speed` is negative. Rahu and Ketu (mean node) are always true. example: false |
| planet.ecl_lat | number | Geocentric ecliptic latitude in degrees (north positive). Decides a graha yuddha: the planet further north wins. Left out for Rahu and Ketu, which sit on the ecliptic. example: -0.000088 |
Usage tips
How to use it
- Path accepts these namessun, moon, mars, mercury, jupiter, venus, saturn, rahu, ketu (case-insensitive, English only). Any other name returns 400 `invalid_param`.
- Several planets?If you need more than one or two planets, call /v1/chart/planets once instead of this endpoint several times.
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.