Tajika timing works by re-casting the birth chart for the moment the Sun comes back to a chosen longitude. The annual chart, varshapravesh, is cast for the instant the Sun returns to its exact natal longitude, which is the birthday to the minute rather than to the day; the monthly chart, maasapravesh, advances that longitude by 30 degrees at a time. This endpoint returns those two plus four progressively shorter subdivisions of the same idea, down to charts that change every couple of minutes.
`date_time`, `latitude` and `longitude` are the birth data. `solaryears` and `solarmonths` say how many returns forward to walk. `date_time_target` is the moment the short-period charts must bracket: for each of them the engine steps the natal solar longitude by a fixed increment (2.5 degrees for the sixty-hour chart, 0.208333 for the five-hour, 0.008 for the twenty-five-minute and 0.0007 for the two-minute) and keeps the crossing that falls closest before your target. `degree_increment` drives the general-purpose chart the same way, so you can choose your own subdivision. `notation` picks 'astrological', which reports positions as sign plus degrees, minutes and seconds, or 'degree' for plain decimals.
The response holds `varshapravesh`, `maasapravesh`, `tajika_chart`, `tajika_sixtyhour`, `tajika_fivehour`, `tajika_twentyfiveminute` and `tajika_twominute`, each a complete Rashi chart with an ascendant and every celestial body carrying longitude, latitude, nakshatra, pada, kakshya, sign and house. The last two are gated behind the booleans `tajika_25min` and `tajika_2min` and come back null unless you ask for them, because each searches hundreds of thousands of solar crossings and is markedly slower than the rest of the call.
Request fields
| Field | Type | Required | Notes |
|---|
| date_time | string (date-time) | required | The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers. |
| date_time_target | string (date-time) | required | |
| degree_increment | number (double) | required | |
| latitude | number (double) | required | Latitude of the place, in decimal degrees. Positive is north, negative is south. Example: 26.9124 for Jaipur, 40.7128 for New York. Minutes and seconds are not accepted - convert first. min -180 · max 180 |
| longitude | number (double) | required | Longitude of the place, in decimal degrees. Positive is east, negative is west. Example: 75.7873 for Jaipur, -74.0060 for New York. Note the sign: a missing minus puts New York in China. min -180 · max 180 |
| name | string | required | |
| notation | string | required | Forwarded to all seven tajika calculations at. |
| solarmonths | number (double) | required | |
| solaryears | number (double) | required | |
| tajika_25min | boolean | required | |
| tajika_2min | boolean | required | |
Full reference for this endpoint