/v1/panchang/summary

All 22 panchang fields in one response.

What this tells you

The `summary` endpoint returns all 22 panchang fields in a single call — equivalent to firing ~15 individual endpoints but costs only 1 credit. Ideal for "daily panchang" cards, widgets, and email newsletters where you need everything at once.

Request

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

example request

curl "https://api.divyastroapi.com/v1/panchang/summary?date=2026-04-19&time=06%3A30&tz=%2B05%3A30&lat=28.61&lon=77.21" \
  -H "Authorization: Bearer dv_live_0123456789abcdef0123456789abcdef"

Response (200 OK)

Successful requests return a JSON body. Field names are stable across versions.

200 response

{
  "date": "2026-04-19",
  "location": { "lat": 28.61, "lon": 77.21, "tz": "+05:30" },
  "tithi":     { "index": 2, "name": "Dwitiya", "paksha": "Shukla" },
  "nakshatra": { "index": 8, "name": "Pushya", "pada": 2, "lord": "Saturn" },
  "yoga":      { "index": 12, "name": "Dhruva", "type": "auspicious" },
  "karana":    { "index": 3, "name": "Gara" },
  "vara":      { "name": "Sunday", "lord": "Sun" },
  "sunrise":   "06:18:42",
  "sunset":    "18:51:20",
  "moonrise":  "11:47:05",
  "moonset":   "23:18:50",
  "rahu_kaal":  { "start": "16:15", "end": "17:49" },
  "yamaganda":  { "start": "12:21", "end": "13:55" },
  "gulika":     { "start": "07:40", "end": "09:14" },
  "abhijit":    { "start": "11:40", "end": "12:29" },
  "brahma_muhurat": { "start": "04:48", "end": "05:36" },
  "hindu_month": { "amanta": "Chaitra", "samvatsara": "Shobhakrit", "paksha": "Shukla", "ritu": "Vasanta" },
  "festivals": []
}

Field reference

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

Field	Type	Meaning
date	string	The requested date. example: `"2026-04-19"`
location	object	Echo of the lat/lon/tz you sent. example: `…`
tithi	object	Same as /v1/panchang/tithi, condensed. example: `…`
nakshatra	object	Same as /v1/panchang/nakshatra, condensed. example: `…`
yoga	object	Same as /v1/panchang/yoga, condensed. example: `…`
karana	object	Same as /v1/panchang/karana, condensed. example: `…`
vara	object	Weekday. example: `…`
sunrise, sunset	string (HH:MM:SS)	Local time strings for easy display. example: `"06:18:42"`
moonrise, moonset	string \| null	Local times. Null on days Moon doesn't rise/set. example: `"11:47:05"`
rahu_kaal, yamaganda, gulika	object	HH:MM local strings for the three inauspicious intervals. example: `{ start, end }`
abhijit, brahma_muhurat	object	HH:MM local strings for the two key auspicious intervals. example: `{ start, end }`
hindu_month	object	Amanta name, samvatsara, paksha, ritu. example: `…`
festivals	string[]	Any festivals falling on this date (from /v1/festivals/on-date). example: `["Chaitra Navratri — Day 2"]`

Usage tips

How to use it

Best default for panchang apps
For most panchang apps, call summary once per (date, lat, lon) and never hit individual endpoints. Cache for 24 hours.
Not for real-time updates
Fields like `hora` and current `choghadiya` slot change during the day — for those, call the dedicated endpoints. Summary returns sunrise-anchored values.

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://divyastroapi.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 500 free credits. Sign up.