API Reference / Vedic Astrology / Panchang
/v1/panchang/abhijit
Abhijit muhurta window.
What this tells you
Abhijit Muhurat is the 8th of the 15 equal daytime muhurtas, so it sits in the middle of the day. It is widely treated as auspicious for starting work or travel. The API divides sunrise-to-sunset on `date` into 15 parts and returns the 8th. Its length is one fifteenth of the daylight span (about 42 minutes in this winter example), not a fixed 48 minutes. Abhijit is not observed on Wednesday. On Wednesdays the API returns a zero-length window: `start_jd` equals `end_jd`, both set to sunrise.
Request
All requests require an Authorization header with your dv_live_* API key.
curl "https://api.lifeastroapi.com/v1/panchang/abhijit?date=2027-01-15&tz=Asia%2FKolkata&lat=28.6139&lon=77.209" \
-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 | 2027-01-15 | Date (YYYY-MM-DD). |
tz | yes | Asia/Kolkata | Timezone: IANA name (Asia/Kolkata) or UTC offset (+05:30). |
lat | yes | 28.6139 | Latitude in decimal degrees. |
lon | yes | 77.209 | Longitude in decimal degrees. |
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": "2027-01-15",
"location": {
"lat": 28.6139,
"lon": 77.209,
"alt": 0
},
"tz": "Asia/Kolkata",
"window": {
"start_jd": 2461420.777406,
"end_jd": 2461420.806641,
"start_local": "2027-01-15 12:09:28",
"end_local": "2027-01-15 12:51:34"
}
}Field reference
Every field in the response, with its type, a real example, and what it means.
| Field | Type | Meaning |
|---|---|---|
| date | string | Echo of the `date` parameter (local date). example: "2027-01-15" |
| location | object | Echo of `lat`, `lon` and `alt` (metres, default 0). example: { "lat": 28.6139, "lon": 77.209, "alt": 0 } |
| tz | string | Echo of the `tz` parameter. The `*_local` times are in this zone. example: "Asia/Kolkata" |
| window.start_jd | number | Start of Abhijit Muhurat, as a Julian Day in UT. On Wednesdays it equals `window.end_jd` (no Abhijit). example: 2461420.777406 |
| window.end_jd | number | End of Abhijit Muhurat, as a Julian Day in UT. example: 2461420.806641 |
| window.start_local | string (YYYY-MM-DD HH:MM:SS) | Start in local time (request `tz`), with no offset suffix. example: "2027-01-15 12:09:28" |
| window.end_local | string (YYYY-MM-DD HH:MM:SS) | End in local time (request `tz`), with no offset suffix. example: "2027-01-15 12:51:34" |
Usage tips
How to use it
- Detect the Wednesday caseThere is no separate flag for the Wednesday rule. Treat a window where `window.start_jd` equals `window.end_jd` as "no Abhijit today" and hide it.
- Default auspicious windowIf an app needs one auspicious time with no other inputs, Abhijit is the usual choice.
- Duration is not returnedCompute it as (window.end_jd − window.start_jd) × 1440 to get minutes.
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.