API Reference / Vedic Astrology / Panchang
/v1/panchang/siddha-yoga
Siddha Yoga check.
What this tells you
A Siddha Yoga here is a weekday + nakshatra pair that classical muhurta texts treat as auspicious for new undertakings, spiritual practice and ceremonies. The API takes the weekday and the Moon's nakshatra at local sunrise of `date` and checks them against a fixed table of 9 pairs. It does not check tithi-based yogas or Sarvartha Siddhi Yoga; for those see /v1/muhurta/shubha-yoga and /v1/muhurta/sarvartha-siddhi. Note that /v1/panchang/advanced reports the first seven of these pairs under the name "Amrit Siddhi" in `panchang_yogas`, and uses the name "Siddha" there for a weekday + tithi rule.
Request
All requests require an Authorization header with your dv_live_* API key.
curl "https://api.lifeastroapi.com/v1/panchang/siddha-yoga?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. |
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": "2027-01-15",
"location": {
"lat": 28.6139,
"lon": 77.209,
"alt": 0
},
"tz": "Asia/Kolkata",
"has_siddha_yoga": true,
"matches": [
{
"weekday": "Friday",
"nakshatra": "Revati",
"weekday_index": 5,
"nakshatra_index": 26
}
]
}Field reference
Every field in the response, with its type, a real example, and what it means.
| Field | Type | Meaning |
|---|---|---|
| date | string (YYYY-MM-DD) | The requested date. example: "2027-01-15" |
| location | object | Echo of lat, lon and alt (metres). example: { "lat": 28.6139, "lon": 77.209, "alt": 0 } |
| tz | string | Echo of the tz you sent. example: "Asia/Kolkata" |
| has_siddha_yoga | boolean | true when the weekday and the nakshatra at local sunrise form one of the Siddha Yoga pairs listed below. example: true |
| matches | array | null | null when has_siddha_yoga is false (not an empty array). Otherwise one object per matching pair with `weekday` (English name), `nakshatra` (English name, short forms such as "P.Bhadra"), `weekday_index` (0 = Sunday) and `nakshatra_index` (0 = Ashwini … 26 = Revati). example: nullJyotish: Pairs checked: Sunday + Hasta, Monday + Mrigashira, Monday + Shravana, Tuesday + Ashwini, Wednesday + Anuradha, Thursday + Pushya, Friday + Revati, Saturday + Rohini, Saturday + Purva Bhadrapada. |
Usage tips
How to use it
- Celebrate in UIWhen `has_siddha_yoga` is true, show a prominent gold or saffron banner. These days are rare and important for muhurta.
- Handle null`matches` is null, not [], when there is no match. Check `has_siddha_yoga` first, or treat null as an empty list.
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.