v0.70 · Integration kit
One API contract. Many approved experiences.
Build server-side consumers with synthetic examples, version discovery and explicit privacy boundaries—without copying calculator logic into every website.
Download and inspect
Start with contracts, not guesswork
Postman collection41 synthetic requests · seven forecasts · twenty-one PDFsJSON samplesKundli, Panchang, all seven prediction routes, classical tools and eight PDF request bodiesOpenAPILive machine-readable schemaCapabilitiesRelease and resource discoveryAccess policyAnonymous access and privacy boundaryMahaguru source evidenceValue-free broader dependency inventory
PDF routes return application/pdf bytes, not a JSON result envelope. Verify HTTP 200, PDF content type, nonempty bytes and the %PDF- signature; a bounded PDF_BUSY response is JSON and can be retried later. Never log a birth or floor-plan request body.
Daily, weekly and monthly Moon-sign, annual sidereal and Western Sun-sign, Nakshatra Tara and personal planner examples are different declared methods. Check engine/calculation/content versions and bilingual fields; none promises a life event.
Moon-sign daily signals now include a bilingual editorial review, rule ID and house-from-Moon evidence for each of seven grahas. Weekly and monthly responses also include bilingual period synthesis. The calculation remains predictions.1; prediction-content.4 adds interpretation and PDF parity without rescoring.
Personal planner timeline days now expose separate gocharaReviews: seven bilingual editorial explanations with rule IDs, matching the unchanged four-field gocharaSignals. Personal calculation remains personal-forecast.1; personal-forecast-content.10 identifies the additional page and PDF explanation. Do not interpret a review as an event verdict.
Personal planner consumers can render result.natalCharts.D1 and D9 directly: both are typed birth charts with twelve houses and planet points. The chartStyle request selects North, South or East layout; it does not change the forecast index. These are not forecast-day transit charts.
The Kundli core response now has typed Lagna, Moon Nakshatra, eleven planet/node rows, Vimshottari periods and twelve-house Rashi, Bhava and Navamsa charts. Use result.charts for positions and result.interpretations for bilingual explanatory text; the calculation is still kundli.2.
Advanced Kundli exposes typed Bhava cusps, thirteen Graha Drishti rows, seven Bhinna and one Sarva Ashtakavarga register, and seven Uccha Bala/own-sign summaries. Use the returned rule profiles and limitations; these scores are not a complete Shadbala or event verdict.
Advanced Kundli also exposes typed result.dashas.vimshottari.mahadashas[].antardashas[].pratyantardashas[], eight Yogini periods and twelve Chara sign periods. Preserve UTC period boundaries and the declared profile when rendering timelines. Yogini includes English and Hindi names; technical Chara evidence still needs Hindi editorial review. These periods are not guaranteed event dates.
For detailed natal topics, use result.natalReadings.topics[]: nine typed topics each include six bilingual reading sections, rule-linked chart facts, reconciliation and optional dated Dasha context. A matching lord is context, not an event promise; traditionalUpaya is intentionally null. These interpretations still require independent expert editorial review.
Server-side examples
Three ways to make the same safe call
cURL
curl -X POST https://theindianastrology.com/api/v2/calculations/panchang \
-H "Content-Type: application/json" \
-d '{"localDate":"2026-09-10","localTime":"12:00:00","timezone":"Asia/Kolkata","latitude":28.6139,"longitude":77.209,"ayanamsha":"lahiri"}'Node.js
const payload = {
localDate: "2026-09-10",
localTime: "12:00:00",
timezone: "Asia/Kolkata",
latitude: 28.6139,
longitude: 77.209,
ayanamsha: "lahiri"
};
const response = await fetch(
"https://theindianastrology.com/api/v2/calculations/panchang",
{
method: "POST",
headers: {
"content-type": "application/json"
},
body: JSON.stringify(payload),
cache: "no-store"
}
);
if (!response.ok) throw new Error("TIA API " + response.status);
const result = await response.json();Python
import httpx
payload = {
"localDate": "2026-09-10",
"localTime": "12:00:00",
"timezone": "Asia/Kolkata",
"latitude": 28.6139,
"longitude": 77.209,
"ayanamsha": "lahiri",
}
response = httpx.post(
"https://theindianastrology.com/api/v2/calculations/panchang",
json=payload,
timeout=20.0,
)
response.raise_for_status()
result = response.json()Integration rules
- Call from your server, not public browser code
- Retain the server-generated response request ID for support
- Validate HTTP status and engine versions
- Never log personal birth payloads
Release boundary
- Public core access may evolve
- No uptime SLA in this release
- No compatibility alias implied
- Native v2 remains authoritative
Ready for an approved consumer
This kit lets a future approved website consume the same frozen first-party calculations without deploying this application to that domain.
Back to API catalogue →Public access policy →Page method and limits पृष्ठ विधि और सीमाएँ
Integration guide: method, evidence and limits
How first-party consumers send requests, handle versions and errors, and keep sensitive inputs out of URLs and logs.
first-party consumers requests, versions और errors कैसे संभालें तथा sensitive inputs को URL व logs से कैसे बाहर रखें।
How it works / कार्यविधि
Use POST bodies for sensitive calculation inputs, record the response version tuple and request ID, and keep retries bounded and idempotent where supported.
sensitive calculation inputs के लिए POST body उपयोग करें, response version tuple व request ID दर्ज करें और retries सीमित व जहाँ समर्थित हों वहाँ idempotent रखें।
Evidence standard / प्रमाण मानक
This route links only to registered source and comparison records. Keep the input summary, engine version, calculation version and intermediate values with the result.
यह route केवल दर्ज source और comparison records से जुड़ता है। परिणाम के साथ input summary, engine version, calculation version और मध्यवर्ती मान सुरक्षित रखें।
Limits / सीमाएँ
Examples cover native contracts only. They do not authorize cross-domain deployment, visitor tracking or storage of birth data.
उदाहरण केवल native contracts के लिए हैं। वे cross-domain deployment, visitor tracking या birth data storage अधिकृत नहीं करते।
Route evidence
Sources and contextual next steps / स्रोत और अगला चरण
The organization maintains the page text and route evidence. Versioned software profiles and tests—not a personal byline—establish numerical reproducibility.
संगठन पृष्ठ सामग्री और route evidence बनाए रखता है। संख्यात्मक पुनरुत्पादकता व्यक्तिगत नाम से नहीं, संस्करणबद्ध software profile और tests से स्थापित होती है।
Registered sources / दर्ज स्रोत
TIA-METHOD-EVIDENCE-1The Indian Astrology versioned calculation-evidence contract / The Indian Astrology संस्करणबद्ध गणना-प्रमाण अनुबंधCalculation-evidence contract / गणना-प्रमाण अनुबंधContinue with context / संदर्भ सहित आगे बढ़ें
Calculation methodologyगणना पद्धतिRelated guideसंबंधित मार्गदर्शिकाRelated guideसंबंधित मार्गदर्शिकाQuestions answered on this page
Frequently asked questions / सामान्य प्रश्न
What does the Integration guide page establish? / Integration मार्गदर्शिका पृष्ठ क्या स्पष्ट करता है?
How first-party consumers send requests, handle versions and errors, and keep sensitive inputs out of URLs and logs. Use POST bodies for sensitive calculation inputs, record the response version tuple and request ID, and keep retries bounded and idempotent where supported.
first-party consumers requests, versions और errors कैसे संभालें तथा sensitive inputs को URL व logs से कैसे बाहर रखें। sensitive calculation inputs के लिए POST body उपयोग करें, response version tuple व request ID दर्ज करें और retries सीमित व जहाँ समर्थित हों वहाँ idempotent रखें।
What is outside this page's scope? / इस पृष्ठ के कार्यक्षेत्र से बाहर क्या है?
Examples cover native contracts only. They do not authorize cross-domain deployment, visitor tracking or storage of birth data.
उदाहरण केवल native contracts के लिए हैं। वे cross-domain deployment, visitor tracking या birth data storage अधिकृत नहीं करते।
Published by The Indian Astrology editorial teamContent modified · Evidence reviewed Source register and provenance →Review licensing and source status →