Changelog

Every change that can affect a response is listed here: new API versions, engine releases and data updates. Each entry names the meta field that changes, so you can match it to stored responses. See Versioning for what is pinned and what is not.

Current versions

meta field	Value
apiVersion	2026-11-01 (the only version)
engineVersion	0.1.0 (pre-release)
bsTableVersion	2026.10.1: published BS 1970 to 2083, projected BS 1956 to 1969 and 2084 to 2157
overridesVersion	null (no overrides yet)
tzdbVersion	unknown (the runtime does not report its release)
deltaTModelVersion	iers-c01-2026.5+quad2100-v1

2026-10-21: Golden corpus v1 and latest accuracy results

No response changes; engine 0.1.0 is unchanged.

• Golden corpus v1 is public: 500 births with the request, our output, Swiss Ephemeris 2.10.03 reference values and the difference for each, plus a summary file. Download links, the format and how to compare with your own reference are on Accuracy.
• The accuracy page now lists the results of the 2026-10-21 run on 5,428 compared births: no hard limit crossed; Moon 4.20″, lagna 4.67″ and dasha dates 0.56 days at worst. Mercury to Saturn miss the 5″ target, at up to 20.24″ for Venus, inside the 60″ hard limit.
• The accuracy page now describes the test sample as it is (5,000 random births and 433 edge cases from a fixed seed) and no longer promises a diff report per release.

2026-10-11: Sunrise default, polar lagna and date range

• Sunrise now defaults to upper_limb_refracted (the upper edge of the Sun, with refraction), as printed Nepali and Indian panchangs use. Before, the default was center_geometric, about 4 minutes later at sunrise. This changes the tithi or nakshatra at sunrise on one or two days a year (for example 2021-11-04 in Kathmandu is now Chaturdashi), and shifts sunset and choghadiya times by a few minutes. Send sunriseConvention: "center_geometric" for the old behaviour.
• Moonrise and moonset no longer depend on sunriseConvention: they are always the moment the Moon’s centre crosses the horizon, as in common panchangs.
• Lagna inside the polar circles (above about 66.5° latitude) could be the setting point instead of the rising one, 180° off. It is now always the rising point.
• One supported window, AD 1900-01-01 to 2100-12-31 (BS 1956-09-19 to 2157-09-15), for every endpoint. AD dates from 1 January to 11 April 1900 now have a BS date. /v1/calendar/convert no longer returns dates after 2100-12-31, and /v1/calendar/month serves every month that lies fully inside the window. supportedRange.bs in GET /v1/meta gains fromDate and toDate.

2026-10-11: Access and metering fixes

Fixes to API version 2026-11-01. Requests that followed these docs keep working; only client tokens issued before this change must be replaced.

• HEAD requests are authenticated, rate limited and charged like the matching GET.
• Unknown paths under /v1 return 404 not_found; methods other than GET, HEAD and POST return 405 method_not_allowed with an Allow header.
• New 503 service_unavailable with Retry-After when credit checks are briefly unavailable and the key cannot be served in degraded mode.
• The test-key daily quota of 100 counts each request’s credit cost, not one per request.
• Publishable keys always carry a monthly credit cap, 2,000 credits by default.
• Client tokens use a new format and tokens issued earlier are refused, so request new ones. A token counts toward the issuing key’s monthly cap and rate-limit bucket, its effective cap is the smaller of its own and the key’s, and it stops within 60 seconds of the key being revoked.
• GET /v1/usage accepts secret keys only.
• A BS panchang range is priced on its AD span.
• GET /v1/places/search returns ambiguous, true when the same name in a birth request would fail with ambiguous_place.
• meta.bsProjectionVersion appears whenever a BS date in the response is projected.
• GET /v1/calendar/month returns 400 invalid_input when only one of lat and lng is sent, and its meta adds engineVersion, tzdbVersion, deltaTModelVersion and overridesVersion.
• MCP: get_panchang returns ambiguous_place with candidates for an ambiguous place name instead of taking the first match.
• topUpUrl points at the dashboard’s billing page.

2026-10-10: Conventions and metadata update

Additive changes to API version 2026-11-01; no request needs to change.

• Two more ayanamshas: raman and kp. See Conventions.
• Bikram Sambat support widened to BS 1957 to 2157. Years outside the published table are returned with status: "projected".
• Every meta now carries deltaTModelVersion. The kundali meta also echoes tradition and sunriseConvention.
• Matching responses (single, batch and rashi) now carry meta.
• subject.offsetSource reports historic_0540 when the pre-1986 Nepal +05:40 convention was applied (previously override).
• Every timestamp is a whole-second ISO 8601 instant, including ambiguous_local_time candidates and /v1/usage expiry times.
• GET /v1/meta accepts any credential, including client tokens, or none.
• Place search ranks places in Nepal higher, more so with lang=ne.
• Some computed instants moved slightly with this update: panchang element times by a few seconds, and dasha boundaries for the sample births by about two minutes. All remain inside the accuracy tolerances.

2026-10-10: Developer docs and beta API

API version 2026-11-01, the first dated version, with engine 0.1.0 and BS table 2026.10.1.

• 16 operations: kundali, graha positions, dashas, guna milan (single, batch) and rashi compatibility, daily and range panchang, BS conversion and month grids, chart SVG, place search, time zones, client tokens, usage and metadata.
• Keys: sk_live_, sk_test_, pk_, client tokens from POST /v1/tokens, and the public demo key with five sample subjects.
• Labels in English, Nepali and Hindi, with Latin or Devanagari digits.
• Errors as RFC 9457 problem details with stable codes.
• The TypeScript SDK, widgets and the MCP server.
• These docs, the API reference, llms.txt and a Markdown copy of every page.

Known gaps in this version, each to be announced here when it ships:

• Public holidays and festivals (/v1/calendar/holidays and /v1/calendar/festivals) wait on the data licence.
• The Samiti tithi override table; until then overridesVersion is null and no override is flagged.
• The golden corpus and per-release diff reports arrive with engine v1.0. See Accuracy.

How to follow changes

This page is the record. Each entry gives the date, what changed and the meta values involved. Breaking API changes are announced at least 12 months before the old version is retired; see the deprecation policy.