Panchanga API
Request the principal Panchanga fields for a date and place. Supply a time to evaluate a particular instant, or omit it for the local-sunrise evaluation when sunrise is available.
POST /v1/vedic/panchanga50,000 credits per monthly allowance · no trial · no automatic overage charges. Plan details ↗
What this API provides.
Calculate tithi, nakshatra, yoga, karana and sunrise-based vara with segment boundaries and explicit Lahiri conventions. Explore a real JSON result.
Numerically evaluated segment boundaries
Sunrise-based traditional vara
Explicit sunrise availability and evaluation policy
Send
- birth.date, IANA timezone, latitude and longitude for the requested place
- Optional local time for an exact requested-instant evaluation
- The supported Lahiri and whole-sign profile options
Receive
- evaluation, at and sunrise_at
- vara and the four angular segment objects
- Start/end boundaries, names, indices and polar-sunrise warnings
Real input. Real output.
Precomputed by the actual calculation engine and response formatter, using synthetic example data. No purchased access or paid provider call was needed.
{
"locale": "en",
"birth": {
"date": "1990-05-21",
"time": "14:30:00",
"timezone": "Europe/Madrid",
"latitude": 40.4168,
"longitude": -3.7038
}
}{
"request_id": "cedb3833ee04e7f1c35f3920d2f9c9e8",
"api_version": "v1",
"locale": "en",
"data": {
"date": "1990-05-21",
"at": "1990-05-21T12:30:00Z",
"evaluation": "requested_instant",
"sunrise_at": "1990-05-21T04:53:39Z",
"vara": {
"index": 1,
"name": "monday"
},
"tithi": {
"index": 27,
"start_at": "1990-05-21T02:11:02Z",
"end_at": "1990-05-21T23:04:43Z",
"paksha": "krishna",
"name": "dvadashi"
},
"nakshatra": {
"index": 27,
"start_at": "1990-05-20T23:53:30Z",
"end_at": "1990-05-21T21:38:21Z",
"name": "revati",
"pada": 3,
"fraction_elapsed": 0.5767318161,
"lord": "mercury"
},
"yoga": {
"index": 3,
"start_at": "1990-05-21T06:07:23Z",
"end_at": "1990-05-22T02:25:07Z",
"name": "ayushman"
},
"karana": {
"index": 53,
"start_at": "1990-05-21T02:11:02Z",
"end_at": "1990-05-21T12:41:49Z",
"name": "kaulava"
}
},
"interpretation": {
"locale": "en",
"kind": "vedic/panchanga",
"disclaimer": "Symbolic reflection, not a verified prediction or professional advice.",
"coverage": {
"total_facts": 4,
"selected_facts": 4,
"omitted_count": 0,
"selection_method": "all-source-facts-v1",
"full_numeric_data_unchanged": true
},
"method": {
"engine": "celestack-original-rules-v1",
"corpus": "celestack-original-compositional-v1",
"corpus_version": "2026-11-17.2",
"fallback_locale": null,
"editorial_status": "agent-authored; independent linguistic review pending",
"predictive_validity": "symbolic interpretations are not scientifically validated predictions",
"chinese_solar_terms": "numeric calendar output only; no rule paragraphs in this corpus"
},
"items": [
{
"fact_id": "vedic/panchanga.nakshatra",
"title": "Revati",
"text": "Calculated lunar mansion: Revati, number 27, pada 3, traditional ruler Mercury. Use this sidereal calendar symbol to reflect on recurring rhythms; it does not determine a personal outcome.",
"source": {
"index": 27,
"start_at": "1990-05-20T23:53:30Z",
"end_at": "1990-05-21T21:38:21Z",
"name": "revati",
"pada": 3,
"fraction_elapsed": 0.5767318161,
"lord": "mercury",
"id": "vedic/panchanga.nakshatra",
"type": "vedic_nakshatra"
}
}
]
},
"warnings": [],
"credits_used": 5
}The response preview selects whole fields and array entries for readability; no numeric values have been replaced. The full download preserves all fields, arrays and interpretation. The request_id is synthetic, and credits_used shows the configured successful-request cost; no credits were consumed.
cURL request — use your own API key and a new idempotency key
curl --request POST 'https://api.celestackapi.com/v1/vedic/panchanga' \
+ --header 'Authorization: Bearer YOUR_API_KEY' \
+ --header 'Content-Type: application/json' \
+ --header 'Idempotency-Key: panchanga-api-example-001' \
+ --data '{
"locale": "en",
"birth": {
"date": "1990-05-21",
"time": "14:30:00",
"timezone": "Europe/Madrid",
"latitude": 40.4168,
"longitude": -3.7038
}
}'Example computed 2026-11-17. Full fixture manifest, engine versions and SHA-256 checksums ↗
Ways to use it.
- A daily Panchanga widget
- Local date and segment-boundary displays
- Calendar data for a developer-controlled traditional interface
12 response locales
English, Ukrainian, Japanese, Spanish, French, German, Portuguese, Arabic, Italian, Hindi, Chinese and Korean.
Calculation values remain language-independent. Localized rule text is agent-authored; independent native-language review remains pending. Machine-readable field names stay stable.
Limits and interpretation.
- The standard sunrise definition is an upper-limb/refraction approximation of −0.8333°. Local terrain and weather are not modeled.
- Without a valid sunrise, a daily sunrise-based Panchanga can be unavailable. Explicit-time angular values can still be returned where supported.
- Muhurta selection, regional festival rules and remedies are not included.
Interpretive content is for symbolic reflection and entertainment. It is not a verified personal prediction or professional advice. Read the API conventions ↗
Choose your billing.
Both options include 50,000 credits per monthly allowance, resetting monthly. No trial and no automatic overage. Custom needs use a contact form.
Saved results: 7-day retention, up to 128 MiB per organization on this initial shared deployment, with a 512 MiB shared retained-result limit. Capacity can return a temporary error; there are no automatic extra charges. Production artifacts have separate retention. All usage and resource limits ↗. Checkout availability is shown in your account.
Frequently asked questions.
What happens when time is omitted?
The endpoint evaluates at local sunrise when available. It reports that choice explicitly rather than claiming an unknown birth time is known.
Does vara change at midnight?
This profile uses the traditional sunrise boundary for vara. A pre-sunrise explicit instant can therefore belong to the preceding traditional weekday.
Does it choose auspicious times?
No. It provides calendar and angular segment data. An auspicious-time recommendation system with regional rules is not part of this endpoint.
What does access cost?
Access is USD 39.99 per month or USD 199 billed annually, with no trial. Both billing options provide 50,000 credits per monthly allowance. 5 credits per successful request or job. Daily credit, attempt, rate and resource limits apply. There are no automatic overage charges.