Technical notes for a responsible Jyotish integration.
This is a product-level overview, not an executable API reference. Ask for the current versioned schema, test access and written commercial scope before implementing against the TKR brand.
What is documented now
The inspected source portal snapshot documents 107 endpoints across 16 families. Areas include Panchang, Kundli, planetary positions, timing, matching and regional calendar workflows. This new website intentionally avoids copying an endpoint table without a verified new-brand API base URL and authentication flow.
Counts are a snapshot, not a promise that every endpoint is included in every commercial tier or offline binary.
Name the astronomical calculation path
The documented choices are tkr_formula (Formula-Lite, an in-house VSOP87-series implementation) and de440 (an in-house reader using NASA JPL's DE440 kernel). The source portal describes explicit provider selection rather than a silent default. For precise date limits and comparisons, request the current technical evidence.
Separate calculation rules from output language
The source snapshot lists 13 named regional choices and 11 accepted response locale values. A language setting does not automatically choose a regional Panchang convention. An integration should record region, location, provider and any relevant ayanamsa or sunrise rule alongside its test cases.
Do not infer an SDK from an API
Formula-Lite is a documented calculation provider. A publicly distributable, platform-specific native SDK is a separate deliverable that needs build, size, accuracy, ABI and licence verification. This site presents offline licensing as an enquiry; it does not host a binary or claim every API family is available locally.
What a technical evaluation should include
- A versioned interface contract for the exact endpoints you will call.
- Credentials and security model for the approved environment.
- Reference calculations with dates, places, providers and conventions.
- Supported date ranges, error cases, limits and localization behavior.
- Separate written commercial terms for hosted calls and offline redistribution.
Need the current integration package?
Share your use case and request the exact versioned contract and evaluation materials.