Standard API
- /api/
- 5 requests/second · burst 20
- Concurrent per source: 12
- Maximum body: 512 KB
- 413 · reduce the body before retrying
- 429 · Retry-After 1s
Public core · Access policy 3
Free to use now. Precise about what that means.
The current core needs no account or API key. That is a release policy—not an uptime SLA, commercial promise or permission to copy the calculation engine.
PDF reports
- /api/v1/reports/
- 1 requests/second · burst 2
- Concurrent per source: 2
- Maximum body: 2048 KB
- 413 · reduce the body before retrying
- 429 · Retry-After 1s
Current contract
Anonymous access without vague promises
| Control | Current state | Machine value |
|---|---|---|
| Authentication | Not required | false |
| API key | Not issued | false |
| Account quota | No account quota; privacy-safe edge limits apply | edge-token-bucket-by-source |
| Rate limiting | 5/sec standard; 1/sec PDF, with short bursts | true |
| Partner environment | Not active | false |
| Browser CORS | Production apex only | https://theindianastrology.com |
| Request/response bodies | Not logged or retained | false |
| Source-address claim | No API access, limit-rejection or body-rejection log; unrelated upstream diagnostics excluded | transient-limit-key-no-api-access-limit-or-body-rejection-log |
| Anonymous access | Current release; not a permanent guarantee | false |
Safe errors
Debug the contract, not the person
Handled application errors and the published 413, 429 and 503 production-edge rejections include a server-generated request ID and versioned code. Validation details name the field and rule but deliberately omit the submitted value. Errors outside this normalized subset—including transport, TLS, malformed-protocol, CORS-policy and intermediary failures—are not promised this envelope.
{
"requestId": "server-generated-id",
"status": "error",
"error": {
"version": "tia-api-error.1",
"code": "VALIDATION_ERROR",
"message": "The request did not match the published contract.",
"fields": [{
"path": "body.birth.timezone",
"code": "string_type",
"message": "Input should be a valid string"
}]
},
"detail": []
}Consumer responsibilities
- Use server-to-server calls outside the apex
- Use exponential backoff for temporary failures
- Never log birth or floor-plan payloads
- Retain response request IDs and engine versions
Release exclusions
- No account or API-key system
- No paid tier or commercial SLA
- No additional CORS origin
- No permanent anonymous-access promise
Machine-readable and reviewable
Integrations should read the live policy instead of assuming that a previous release’s access rules still apply.
Inspect the live access policy ↗Open integration guide →Page method and limits पृष्ठ विधि और सीमाएँ
Public API access policy: method, evidence and limits
The anonymous-core access boundary, CORS scope, fair-use expectations and future first-party controls.
anonymous-core access सीमा, CORS क्षेत्र, fair-use अपेक्षाएँ और भविष्य के first-party controls।
How it works / कार्यविधि
The active public API is same-origin and stateless; callers must minimize personal data, respect resource limits and preserve calculation provenance.
सक्रिय public API same-origin और stateless है; callers निजी डेटा न्यूनतम रखें, resource limits मानें और calculation provenance सुरक्षित रखें।
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 / सीमाएँ
Anonymous availability is not an unlimited service guarantee. Credentials, quotas and partner access require a separately approved business layer.
Anonymous उपलब्धता असीमित सेवा गारंटी नहीं। credentials, quotas और partner access के लिए अलग स्वीकृत business layer चाहिए।
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 Public API access policy page establish? / सार्वजनिक API access नीति पृष्ठ क्या स्पष्ट करता है?
The anonymous-core access boundary, CORS scope, fair-use expectations and future first-party controls. The active public API is same-origin and stateless; callers must minimize personal data, respect resource limits and preserve calculation provenance.
anonymous-core access सीमा, CORS क्षेत्र, fair-use अपेक्षाएँ और भविष्य के first-party controls। सक्रिय public API same-origin और stateless है; callers निजी डेटा न्यूनतम रखें, resource limits मानें और calculation provenance सुरक्षित रखें।
What is outside this page's scope? / इस पृष्ठ के कार्यक्षेत्र से बाहर क्या है?
Anonymous availability is not an unlimited service guarantee. Credentials, quotas and partner access require a separately approved business layer.
Anonymous उपलब्धता असीमित सेवा गारंटी नहीं। credentials, quotas और partner access के लिए अलग स्वीकृत business layer चाहिए।
Published by The Indian Astrology editorial teamContent modified · Evidence reviewed Source register and provenance →Review licensing and source status →