/v1/panchang/gulika

Gulika interval.

What this tells you

Gulika Kaal (Gulika is called the son of Saturn) is the third daily window that almanacs list with Rahu Kaal and Yamaganda. It is avoided for new beginnings. The daylight span (sunrise to sunset on `date`) is divided into 8 equal parts and one part is picked by weekday: Sunday 7th, Monday 6th, Tuesday 5th, Wednesday 4th, Thursday 3rd, Friday 2nd, Saturday 1st. It lasts one eighth of the daylight span.

`*_jd` values are Julian Days in UT. `*_local` strings are local wall-clock time in the request `tz`, formatted "YYYY-MM-DD HH:MM:SS" with no offset. The `time` parameter does not change the result. If the Sun does not rise or set on `date` (polar day or night) the API returns 422 `data_unavailable`.

Request

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

example request

curl "https://api.lifeastroapi.com/v1/panchang/gulika?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.

200 response

{
  "date": "2027-01-15",
  "location": {
    "lat": 28.6139,
    "lon": 77.209,
    "alt": 0
  },
  "tz": "Asia/Kolkata",
  "window": {
    "start_jd": 2461420.627578,
    "end_jd": 2461420.682393,
    "start_local": "2027-01-15 08:33:43",
    "end_local": "2027-01-15 09:52:39"
  }
}

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 Gulika Kaal, as a Julian Day in UT. example: `2461420.627578`
window.end_jd	number	End of Gulika Kaal, as a Julian Day in UT. example: `2461420.682393`
window.start_local	string (YYYY-MM-DD HH:MM:SS)	Start in local time (request `tz`), with no offset suffix. example: `"2027-01-15 08:33:43"`
window.end_local	string (YYYY-MM-DD HH:MM:SS)	End in local time (request `tz`), with no offset suffix. example: `"2027-01-15 09:52:39"`

Usage tips

How to use it

Pair with Rahu Kaal and Yamaganda
Call /v1/panchang/rahu-kaal and /v1/panchang/yamaganda too, or use /v1/panchang/advanced, which returns all three under `muhurta` in one response.
This is a time window, not a chart point
The response is the Gulika Kaal time window only. It does not give the longitude or sign of Gulika as an upagraha.
Duration is not returned
Compute 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.