AstroLogics API

Changelog

Every AstroLogics API change, newest first: new operations, calculation changes with their engine version, and corrections. RSS

2026-11-09 — A clearer daily test-call limit message

Changes (no new error code, and nothing removed or renamed)

  • When a project's test keys reach the daily test-call cap, the 429 quota_exhausted message now also says that a live key has no daily cap and spends the plan's monthly credits (3,000 on Free), and where to create one. The status, error code and Retry-After are unchanged.

2026-11-06 — A sign-up code, and branded emails

Additions (nothing removed or renamed, and no API change)

  • The sign-up email now carries a 6-digit code beside the link: type it on the page that asked for it, handy when the email is open on another device. The code lasts 30 minutes; the link still works for 24 hours.
  • Account, alert and billing emails now come in the AstroLogics layout, with the link also written out in full. The plain-text part is unchanged.

2026-11-05 — An interactive home page

Additions (nothing removed or renamed, and no API change)

  • The home page now runs on the API itself: a kundli you can redraw with your own birth details, today's panchang for a city, a sample Ashtakoot match and today's reading for each sign, each with the code for the same call in four languages.
  • Also on the home page: today's panchang and all twelve signs, an assistant answering through the MCP server with today's figures, the widgets running live with colours and a snippet to copy, a filter by category for the operations with a sample response for each, and the credit calculator.
  • The widgets now style themselves on pages whose Content-Security-Policy blocks inline styles (a constructed stylesheet, where the browser has one). The WordPress plugin carries the same script.
  • A more compact footer on every page.

2026-11-04 — A page for each operation; developer tools; pages in Hindi; FAQ, glossary, About and topic pages; clearer titles; schema.org markup; llms-full.txt

Additions (nothing removed or renamed)

Corrections

  • Product and reference pages are titled by what they are, such as "Kundli API" and "Kundli matching API". Twelve docs pages that had no main heading now have one.
  • The sign-up page pointed search engines to an address that does not exist. The Google tag no longer loads on sign-up and reset links, whose address carries a one-time token; it did before, against our own rule.

2026-11-03 — Engine 2026.10.10: first mahadasha's sub-periods and Ashtakoot scores corrected; paid plans open; n8n and WhatsApp guides; contact page; prices in INR only; blog

Calculation changes (engine 2026.10.10)

  • Vimshottari: the sub-periods of the first mahadasha were all squeezed into the balance left at birth. They now skip the part before birth, so the first one returned is the one running at birth. Mahadasha dates and every later period are unchanged. This covers /v1/dasha/vimshottari, the running period, and anything built on them.
  • Ashtakoot: Yoni, Vashya, Graha Maitri, Gana and Tara now follow published tables, named in conventions. Some totals change, mostly downward. The old rules were simplified: for example, hostile Yoni pairs scored 1 and Graha Maitri never scored 0.
  • Transit scoring: Mars in Taurus, Venus in Leo and Mercury in Sagittarius were wrongly marked debilitated. The correct signs are Cancer, Virgo and Pisces, which were already there.
  • Western: passing some orbs now removes the extra 2° for the Sun and Moon on every aspect, as the docs and sun_moon_extra say. Before, it stayed on aspects you did not list.
  • Hindi text: wheel labels, a transit sentence, and spellings made consistent. Machine ids are unchanged.

Additions (nothing removed or renamed)

  • Paid plans are open: choose Starter, Growth or Business on pricing, and pay by UPI, card or net banking through Razorpay.
  • n8n guide, with two workflows you can import, and a WhatsApp guide covering AiSensy, Gupshup, Interakt, LeadNXT and WATI.
  • A contact page.
  • A blog, starting with posts on historical timezones in Indian birth charts, how Vimshottari dasha is calculated, and the panchang in Hindi. Every figure in a post is checked in our tests against the API.
  • Western house cusps are now checked in our tests against Swiss Ephemeris. No results changed.

Corrections

  • Prices are now shown in INR only. For billing in USD, write to us.
  • The home page and caching and data retention said query strings are never written to our logs. The web server's access log does keep them for up to 8 days, as the privacy policy has said. Send birth details in a POST body.

2026-11-02 — Vastu; South Indian matching; Pythagorean numerology; Vedic additions; suggested paths on a 404; AGENTS.md; accuracy measured again; MCP servers

Additions (nothing removed or renamed)

  • Shopify guide: the panchang and horoscope widgets on a Shopify store, with a publishable key.
  • Tutorials: a kundli page in Next.js and a kundli screen in Flutter.
  • SDKs for TypeScript and JavaScript, Python and PHP, downloadable from this site, with quickstarts for TypeScript, Python and PHP. A new page for the MCP servers.
  • Feng Shui: /v1/feng-shui/kua, house, flying-stars, flying-stars.svg and annual.
  • Chinese: /v1/chinese/bazi, luck-pillars, annual, compatibility, zodiac, date and solar-terms.
  • Western: /v1/western/chart, chart.svg, aspects, synastry, composite, transits, progressions, solar-return and lunar-return.
  • Biorhythm: /v1/biorhythm/reading, forecast, critical-days, compatibility, phases and daily.
  • Forecast: /v1/forecast/timeline, transits, significant-dates, digest and solar-return.
  • Widgets: panchang, horoscope, kundli, matching and Vastu on any page with one script tag, and a WordPress plugin with blocks and shortcodes.
  • White-label reports: /v1/reports/kundli.pdf, /v1/reports/match.pdf and /v1/reports/vastu.pdf, under your name, logo and colour, in English or Hindi.
  • More Vedic and KP: /v1/kundli/chara-karakas, /v1/kundli/bhav-chalit, /v1/kp/changes, /v1/kp/ruling-intervals, /v1/transits/aspects and /v1/transits/parallels.
  • Vedic additions: /v1/kundli/upagrahas, /v1/kundli/arudha, /v1/planets/asta for Asta and Uday at a place, /v1/planets/series for positions over a range, and /v1/reference/rashis and /v1/reference/nakshatras.
  • /v1/match/dashakoot: the ten poruthams, each with its count and result, and Rajju called out.
  • /v1/match/papasamyam: malefics from lagna, Moon and Venus in both charts, compared. Choose the count or weighted method, because sources differ on the points.
  • /v1/numerology/pythagorean: core numbers, karmic debts and lessons, pinnacles, challenges and personal year.
  • Vastu: seven operations for a real plot. The mandala on 81 or 64 squares in metres, drawn as SVG, the door's pada, plot and room findings, and the Ayadi formulas, in English and Hindi. Rules cite their source or are labelled convention; see Vastu conventions.
  • ?compact=1 on the MCP server: shorter tool lists, and calls that answer without meta.
  • MCP servers: every public operation as a tool at https://api.astrologics.in/mcp, charged as REST is, and the docs at https://developers.astrologics.in/mcp, no key needed.
  • error.suggestions on a 404 for an unknown path: the operations you may have meant, including the right method for the right path. Absent when nothing is close.
  • AGENTS.md: notes for coding agents, beside llms.txt.
  • The accuracy figures and test set are measured again against NASA JPL Horizons, on the current engine.

2026-10-30 — tone=descriptive; stable ids for tithi notes and insights

Additions (nothing removed or renamed)

  • options.tone (POST) and ?tone (GET): descriptive puts reviewed descriptive sentences in the prose fields of GET /v1/panchang (tithi.note), POST /v1/timing/favourable-days (each day's description), /timing/personal (today.summary, today.insights), /timing/dasha-transit (insights), /transits/natal (each description, read from the Moon) and GET /v1/transits/events (each note), in options.lang / ?lang (en, hi). Every sentence is attributed to the tradition and none is an instruction. Ids, scores and every other value are unchanged; the bundle tones its members. Same credits.
  • insight_ids beside insights on /timing/personal (today) and /timing/dasha-transit: one stable id per insight (maha_transit_favourable, maha_transit_challenging, maha_strong, maha_debilitated, antar_strong, antar_weak, both_aligned, both_stressed), in both tones.
  • GET /v1/transits/events takes lang.

Changes

  • GET /v1/panchang: tithi.note_id is tithi_<name> (tithi_pratipada … tithi_purnima, tithi_amavasya) in both tones. It was a slug of the sentence, so it changed whenever the sentence did.

2026-10-29 — Five more operations; transit events complete; /v1/transits on the right day; the dasha balance at full precision

Calculation changes

  • engine_version 2026.10.9.
  • POST /v1/dasha/vimshottari and /current (and the Yogini dasha in /v1/kundli/classical): the balance at birth is computed from the Moon at full precision. It used the Moon rounded to 4 decimals, which moved every boundary by up to about 35 minutes for an 18-year lord (23 minutes for 2000-01-01 12:00 UTC: Rahu now ends 2000-09-18 13:21:28 UTC).
  • GET /v1/transits/events: Ketu's sign changes are listed (none were: every Ketu sample failed), at Rahu's moment; every eclipse in the range is listed (it stopped at three solar and three lunar); an eclipse's sign is the sidereal sign of the eclipsed body (it was null). Events are sorted by instant.
  • GET /v1/transits: each change is dated on the IST day it happens, from its exact moment (it sampled UTC midnights and gave the day after).

New operations

  • POST /v1/kundli/bundle: several chart operations in one call (kundli, divisional, dasha, current_dasha, yogas, ashtakavarga, outer, classical, wealth, gemstones, numerology, shadbala, natal_transits, year_outlook[:year]), each member's data as its own operation returns it; at is the instant for current_dasha, ashtakavarga and natal_transits. One rate-limit slot; charged the members' sum less one credit.
  • POST /v1/muhurat/scan (3 credits): up to 62 days for an activity within daily hours, with exclude_dates: the favourable choghadiyas and Abhijit left after Rahu Kaal, Yamaganda and Gulika, clipped to the hours; the ten best days.
  • GET /v1/outer-planets/cycle (1 credit, publishable): the stations of Saturn, Uranus, Neptune or Pluto to the minute, and whether it is retrograde now, since when and until when.
  • GET /v1/horoscope/weekly/rashi-tones (1 credit, publishable): each rashi's 0–100 score for each day of a week, its band, best and worst days and the planet behind it. Structure only.
  • GET /v1/planets/now (1 credit, publishable): the positions at the top of the current hour, with meta.valid_until.

Additions (nothing removed or renamed)

  • GET /v1/transits/events: at (the exact instant), note_id (a stable id for the note's template) and include_nodes (the true node's stations). GET /v1/transits: at.
  • POST /v1/dasha/vimshottari and /current: basis (the full-precision Moon, the ayanamsa, the nakshatra and its degrees, the elapsed and remaining fractions, the balance in years and days, the year length) and options.dasha_year (365.25, the default; 365.2422; 360).

2026-10-29 — Three new operations; transits in the ashtakavarga; as_of on the timing operations

New operations

  • POST /v1/timing/year-outlook: twelve months of the slow planets' transit houses from the lagna, scored, with the best and worst runs of months. Ids and numbers only.
  • POST /v1/kundli/wealth: the D2 hora placements, the D10 lagna and 10th lord, vargottama planets and the D1, D2, D9 and D10 scores, with an overall 0–10. No buy/sell signal and no sentences.
  • POST /v1/kundli/gemstones: the lagna lord's, the 9th (or 5th) lord's and the mahadasha lord's stones, and those to avoid, by functional lordship. classical.lucky.gem (the rashi lord's stone) is unchanged.

Additions (nothing removed or renamed)

  • POST /v1/kundli/ashtakavarga: transits (the bindus of the sign each planet occupies at at, default now), best_signs and as_of. The request takes at.
  • POST /v1/varshaphal: planets (the nine grahas in the solar-return chart) and year_lord_placement.
  • POST /v1/timing/personal, /timing/dasha-transit and /timing/favourable-days: as_of, a date read as local noon at the birth place. /timing/favourable-days also takes at.
  • GET /v1/transits/graha-yuddha: each war's until, when the pair is next more than 1.5° apart.
  • Stable ids beside the engine's sentences: tithi.note_id (panchang), description_id (favourable days) and today.summary_id (personal timing). The same sentence always has the same id.
  • The OpenAPI document publishes the 27 nakshatra ids (NakshatraId) on the kundli, panchang and favourable-days fields.
  • engine_version is unchanged (2026.10.8): no calculation changed.

2026-10-29 — Ashtakavarga totals; the solar return to the second

Calculation changes

  • engine_version 2026.10.8.
  • POST /v1/kundli/ashtakavarga and POST /v1/kundli/classical (prastara): five rows of the benefic-place table are now Parashara's (Sun from the Moon and from Venus, the Moon from Jupiter, Venus from itself and from the lagna). Every chart's totals are now the classical Sun 48, Moon 49, Mars 39, Mercury 54, Jupiter 56, Venus 52, Saturn 39 and Sarva 337. They were Sun 53, Moon 48, Venus 53 and Sarva 342 on every chart.
  • POST /v1/varshaphal: solar_return is found to the second. The search could stop up to a few minutes short of the return (01:46 for a return at 01:47:41), and births outside India were read on Indian time, which put the natal Sun hours off. The annual lagna, muntha house, year lord and mudda dasha follow the corrected moment.

2026-10-29 — Yamaganda, Gulika, Abhijit, the true node, natal transits

API changes

  • options.node works: "mean" gives Rahu and Ketu at the mean node wherever an operation uses the nodes, and meta.node says mean. It was accepted and ignored. POST /v1/planets/positions still returns both nodes by name.
  • POST /v1/transits/natal returns the transits. It always returned an empty list. Each one's house_from_moon counts from the natal Moon's sign (the impact is judged from it), natal_house from the lagna; without a birth time natal_house is left out, with a time_unknown warning. impact can now also be neutral (those were served as favourable).

Calculation changes

  • engine_version 2026.10.7.
  • GET /v1/panchang: yamaganda and gulika_kaal were in the wrong part of the day on every weekday. They now follow the classical tables (Yamaganda in parts 5, 4, 3, 2, 1, 7, 6 of the eight from sunrise, Sunday first; Gulika in 7, 6, 5, 4, 3, 2, 1). New Delhi, 29 Oct 2026: Yamaganda 06:31–07:54, Gulika 09:18–10:41, as Drik Panchang gives. rahu_kaal was right and is unchanged.
  • abhijit is the 8th of the day's 15 muhurtas (a fifteenth of sunrise to sunset, centred on local noon): 11:42–12:27 at New Delhi on 29 Oct 2026, as Drik gives. It was a fixed 48 minutes around noon.
  • The true node is the osculating node, as Swiss Ephemeris and Drik define it. It was Meeus' periodic series, up to 17′ away; now within 1′ of Drik and equal to Swiss Ephemeris to the arc-second. Rahu and Ketu move on every chart (by minutes of arc), so near a boundary their nakshatra, pada, navamsa or KP lords can change. The mean node is unchanged.
  • Transit descriptions use ordinals ("1st", "2nd", "3rd"); they read "1th", "2th", "3th".

2026-10-19 — Sade Sati ends when Saturn really leaves

API changes

  • POST /v1/dosha/sade-sati gains legs: each sign leg of the Sade Sati or Dhaiya running now (type, sign, phase udaya/shikhar/asta, start, end), as POST /v1/dosha/sade-sati/timeline reports them, a retrograde return included. Empty when neither is running. Nothing removed or renamed.

Calculation changes

  • engine_version 2026.10.6. end_date is the IST date Saturn leaves the last sign of the window for good, from the same exact ingress search as the timeline. It was an average Saturn speed added to the day of the call, so it moved with the clock and could be months off (Moon in Aries: 2032-11-19 before, 2032-05-31 now).

2026-10-19 — Business-name numbers for master totals

Calculation changes

  • engine_version 2026.10.5. POST /v1/numerology/business-name: a name whose letters total a master number (11, 22 or 33) now gets that number's root (2, 4 or 6) as business_number, with its planet, verdict and note. It returned the master number with an empty planet and the note for 1. Every other name is unchanged.

2026-10-17 — Planetary events; richer panchang, muhurat, positions and KP answers

API changes

  • New: GET /v1/transits/events (listPlanetaryEvents, 1 credit, publishable): every sign change of the Sun, Mercury, Venus, Mars, Jupiter, Saturn, Rahu and Ketu, every retrograde and direct station, and the solar and lunar eclipses between two dates or instants, with the IST time to the minute. 68 operations.
  • GET /v1/panchang: tithi.note, nakshatra.number, nakshatra.hours_remaining, yoga.number.
  • GET /v1/panchang/choghadiya: timezone; each period's is_current and minutes_left (at the moment of the call).
  • POST /v1/timezone: ambiguous (the local time falls in a daylight-saving change).
  • GET /v1/muhurat/search: optional janma_nakshatra, janma_rashi (tara and chandra bala) and top; every day carries its weekday, panchang, factors, panchak flags and personal balas; best (the top usable days with their windows), activity_info, advisories, disclosure, counts; the range is now 1–400 days (was 1–90).
  • GET /v1/horoscope/{sign} and GET /v1/horoscope with lang=hi: hindi, the whole Hindi reading (areas, lucky colour, number and day).
  • POST /v1/planets/positions: send date + time (the local wall clock at the place) instead of datetime if you prefer; each body gains nakshatra_lord, sub_lord (KP), combust, dms and speed; the answer gains local, ayanamsa and julian_day.
  • GET /v1/kp/ruling-planets: local, weekday, lagna_sign, moon_sign, nakshatra. GET /v1/kp/horary: division.number, division.midpoint, sub_sub_lord, question_groups.
  • POST /v1/timing/dasha-transit: optional at (any moment; default now): the periods running then against the sky then.
  • POST /v1/timing/eclipses: the per-eclipse impact sentence is no longer served (date, kind, type, sign, natal house, intensity and shadow end stay).
  • Nothing else removed or renamed.

Calculation changes

  • None: engine_version stays 2026.10.4.

2026-10-17 — Graha yuddha summaries; the nakshatra weight

API changes

  • GET /v1/transits/graha-yuddha: each war gains summary, the engine's one-sentence reading (the pair, the sign, who wins and who is weakened).
  • GET /v1/panchang: nakshatra gains weight, the engine's weighting of the Moon's nakshatra for the day (-0.22 to 0.25).
  • No field removed or renamed; 67 operations, as before.

Calculation changes

  • None: engine_version stays 2026.10.4.

2026-10-17 — Numerology responses carry the whole reading

API changes

  • POST /v1/numerology/core gains hidden_passion, maturity, personal_year, personal_month, personal_day, life_path_meaning (name, keyword, traits), soul_urge_meaning, personality_meaning, lucky_colors, lucky_days, lucky_gem and name_breakdown; name is now optional (the reading from the date alone, with the name numbers null).
  • POST /v1/numerology/name gains soul_urge, personality, hidden_passion and letter_breakdown.
  • POST /v1/numerology/mobile gains digits, count, planet, note, favourable and tip; number may carry the separators people type and be as short as four digits (the API reads its digits).
  • POST /v1/numerology/loshu gains present, notes, arrows (strength and weakness lines), driver, conductor and summary.
  • POST /v1/numerology/compatibility gains person_a, person_b, scores, verdict and guidance; each person's name is now optional.
  • POST /v1/numerology/name with a name that has no letters now answers 400 invalid_parameter (it answered 500).
  • No field removed or renamed; 67 operations, as before.

Calculation changes

  • None: engine_version stays 2026.10.4.

2026-10-17 — 14 new operations: timing, the classical layer, muhurat days and dated muhurat lists; tithi and nakshatra end times

API changes

  • Timing (new group): POST /v1/timing/personal (today's score and band, the dasha–transit reading, a day strip and any red zone), POST /v1/timing/dasha-transit (the running mahadasha and antardasha lords against their transits), POST /v1/timing/favourable-days (tara bala from the birth star, day by day) and POST /v1/timing/eclipses (the eclipses of the months ahead over the chart). Where the engine reads the clock, as_of says the instant and meta.as_of carries it.
  • Kundli: POST /v1/kundli/classical (house cusps, bhava bala, prastara ashtakavarga, graha avasthas, sthira karakas, lucky points), POST /v1/kundli/outer-planets (Uranus, Neptune, Pluto with house readings in English and Hindi) and POST /v1/kundli/d12 (the Dwadasamsa read for the lineage).
  • Doshas: POST /v1/dosha/sade-sati/timeline, every Sade Sati and Dhaiya leg of a lifetime (years 1–120, default 90).
  • Transits: GET /v1/transits/graha-yuddha, planetary war now (publishable).
  • Panchang & muhurat: GET /v1/muhurat/day, one day judged for an activity with the windows left after Rahu Kaal, Yamaganda and Gulika (publishable); GET /v1/muhurat/{occasion}/year and GET /v1/muhurat/{occasion} (vivah, grihapravesh, vehicle, property), the dated muhurat lists behind astrologics.in's yearly pages, with each day's windows or its reason (publishable, 2 credits each).
  • Numerology: POST /v1/numerology/business-name and POST /v1/numerology/lucky-name.
  • GET /v1/panchang gains tithi.ends_at and nakshatra.ends_at: when the tithi and nakshatra running at local noon end, on the place's clock. No other field changes. 67 operations in all.

Calculation changes

  • None: engine_version stays 2026.10.4. Eclipses are a new calculation (astronomy-engine's global searches, checked against NASA's 2026–2028 catalogue to the day), not a change to an existing one.

2026-10-03 — One year length for every dasha

Calculation changes

  • engine_version 2026.10.4. Yogini and Chara dashas now use 365.25-day years, as Vimshottari always has. They used 365.2425-day years, so their dates drifted from Vimshottari's convention by about 6 hours over 35 years, and more with age. Positions and Vimshottari are unchanged.

2026-10-03 — Sidereal positions without nutation; dashas from the birth time

Calculation changes

  • engine_version 2026.10.3. Every sidereal longitude (grahas, lagna, house cusps) moves by the nutation in longitude at that moment, at most 17″; Rahu and Ketu do not move. We now subtract the true ayanamsa (mean Lahiri plus nutation), as Swiss Ephemeris does, so sidereal positions no longer carry nutation. Checked against NASA JPL Horizons: the Moon on 9 Feb 1976 at 16:00 UT moved from 0.22′ ahead of JPL to within 2″ of it.
  • Vimshottari, Yogini and Chara dashas now start at the birth instant. They started at 00:00 UTC on the birth date, so every period began and ended up to a day early.
  • Antardasha, pratyantardasha and sookshma boundaries are now exact fractions of their parent, and the last one ends exactly when its parent does. Each length used to be rounded before the next was added, so the errors summed: one antardasha ended 8 h 46 m before its mahadasha.
  • Together these move Vimshottari dates by up to about two days; a sign or nakshatra changes only for a graha within 17″ of a boundary, and a divisional sign only for one near a division's edge.

2026-09-25 — Choose the ayanamsa

API changes

  • options.ayanamsa accepts lahiri (the default), raman, krishnamurti, yukteshwar and fagan_bradley on chart operations. meta.ayanamsa names the system used. KP operations always use KP-New, and the personal muhurat, panchang and calendar stay on Lahiri (Chitrapaksha).

Calculation changes

  • engine_version 2026.9.28. Nothing moves unless you choose a system: Lahiri results are byte-identical.
  • Each system is its Swiss Ephemeris definition, a constant offset from Lahiri: Fagan-Bradley +52′59″, Krishnamurti −5′49″, Yukteshwar −1°22′43″, Raman −1°26′47″.

2026-09-25 — Holika Dahan and Holi

API changes

  • GET /v1/calendar/festivals adds Holika Dahan (its muhurat, Bhadra Punchha and Bhadra Mukha) and Holi, the next day.

Calculation changes

  • New calculations only; engine_version stays 2026.9.27.
  • Holika Dahan follows Drik Panchang's stated Bhadra rules, in order: the pradosh after Bhadra; else from Bhadra's end to midnight; else the Bhadra Punchha before midnight; else the next day's pradosh when Purnima lasts 3.5 prahars into it; else the pradosh outside Bhadra Mukha. Checked against Drik's New Delhi dates for 2024 to 2028 and the Government of India's 3 March 2026. For 2028 Drik prints a window that overlaps its own Bhadra Mukha; we give the pradosh after Bhadra.

2026-09-25 — Hindi panchang labels, and karana names

API changes

  • lang=hi now gives the panchang's tithi, nakshatra, yoga, karana and vara labels in Hindi, and the choghadiya's too. Machine ids stay English. Choghadiya periods gain a label (English by default).

Calculation changes

  • engine_version 2026.9.27.
  • Karana names: the last three half-tithis of a lunar month are Shakuni, Chatushpada and Naga. They were served as Chatushpada, Naga and a blank name (an off-by-one in the engine), so Shakuni never appeared. Karana numbers were right.

2026-09-25 — Six more festivals

API changes

  • GET /v1/calendar/festivals adds Makar Sankranti, Maha Shivaratri, Rama Navami (with its Vaishnava date), Raksha Bandhan, Krishna Janmashtami and Ganesh Chaturthi, each with its windows (punya kaal, nishita, Madhyahna, the rakhi window) and moments.

Calculation changes

  • New calculations only; engine_version stays 2026.9.26 and no existing result moves.
  • Makar Sankranti: the day of the Sun's sidereal entry into Makara, or the next day if it enters after sunset. Maha Shivaratri and Janmashtami: the night whose nishita the tithi covers most. Rama Navami and Ganesh Chaturthi: the day whose Madhyahna (the middle fifth of daytime) the tithi covers most; Rama Navami's Vaishnava date is the day whose sunrise the Navami holds. Raksha Bandhan: Shravana Purnima after Bhadra, in the Aparahna, else the pradosh, else the next morning while the Purnima lasts.
  • Each was served only after its 2026 date matched two or more published sources (Drik Panchang, Prokerala, the Government of India's holiday lists), with windows within 3 minutes. Holika Dahan and Holi are held back: 2026's date follows a Bhadra exception the published rule does not state.

2026-09-25 — Panchang outside India, and Amavasya

API changes

  • Where the Sun does not both rise and set on a date (polar latitudes), the panchang, choghadiya and muhurat searches now answer 400 (invalid_parameter, lat) instead of an approximate time.

Calculation changes

  • engine_version 2026.9.26 (the second engine release of 25 September).
  • Panchang and choghadiya outside the IST zone were on India's clock: London's sunrise read 11:33 instead of 06:03, Dubai's was 90 minutes late, and New York's came from an approximation. Sunrise, sunset, Rahu Kaal, Gulika, Yamaganda, Abhijit and every choghadiya period are now on the place's own clock, daylight saving included. The day's tithi, nakshatra, yoga and karana are read at the place's local noon, not noon in India. Results for places in India do not move.
  • Tithi 30 is named Amavasya. It was called "Purnima" (Krishna paksha) in the panchang.
  • The weekday no longer depends on the server's time zone.

2026-09-25 — Festivals

API changes

  • GET /v1/calendar/festivals (2 credits; publishable keys too): the festivals of a year at a place. It covers Pitru Paksha (16 shraddhas, Maha Bharani, Magha), Sharad Navratri, Sandhi Puja, Vijayadashami, Sharad Purnima, Valmiki Jayanti, Karwa Chauth, Ahoi Ashtami, Dhanteras, Narak Chaturdashi, Kali Chaudas, Diwali, Govardhan Puja, Bhai Dooj, Akshaya Navami, Kartik Purnima and Dev Deepawali. Each comes with its rule, its tithi, its windows (Aparahna, pradosh, Lakshmi Puja …) and its moments (moonrise, star sighting). 53 operations in all.

Calculation changes

  • New calculations only: engine_version stays 2026.9.25 and no existing result moves.
  • Each festival is found in its nija lunar month (an adhik month is skipped) on the first local day that meets its own rule (Aparahna, sunrise, sunset and pradosh, moonrise, midnight). Where no day does, a named fallback applies and flags says so.
  • Moonrise follows the panchang convention: the Moon's centre on the true horizon. Lakshmi Puja is the pradosh within the Vrishabha (fixed) lagna.
  • Checked against the 2026 festival dates and times astrologics.in published and cross-checked with published panchangs (Drik Panchang, Belur Math and others): all agree within their stated tolerances. verified marks 2026; other years follow the same rules.

2026-09-25 — Tithi calendar and Ekadashi

API changes

  • Calendar: GET /v1/calendar/tithis gives every tithi's start and end between two dates (up to 62 days) and the tithi at each local sunrise; GET /v1/calendar/ekadashi gives every Ekadashi of a year with its vrat date, tithi and paran window. One credit each; both accept publishable keys.
  • The conventions now state the lunar month (amanta, with purnimanta names alongside). 52 operations in all.

Calculation changes

  • engine_version 2026.9.25. New calculations only: no existing result moves.
  • Tithi start and end to the minute (the Moon–Sun elongation, found by bisection). They are the same everywhere; the tithi at sunrise depends on the place.
  • Ekadashi date (Smarta): the local day whose sunrise the Ekadashi tithi covers. If it covers no sunrise, the day it begins; if it covers two, the first. Both cases are flagged.
  • Paran is our own rule, labelled rule_by: astrologics in every response: from the later of sunrise on the next day and the end of Hari Vasara (the first quarter of Dwadashi), to the end of Dwadashi.
  • Vaishnava date (Dashami at arunodaya, 96 minutes before sunrise, moves the fast a day on) appears only where it differs; its paran is not computed.
  • Checked against the six 2026 Ekadashis published on astrologics.in: dates, tithi and paran times agree to the minute.
  • Sunrise is found from the place's own midnight, so it is right outside India too. Where the Sun does not rise on every day, the request is refused rather than answered with a guess.

2026-09-25 — 17 new operations: KP, Lal Kitab, Varshaphal and more

API changes

  • KP: chart with star, sub and sub-sub lords; 4-step significators and house groups; ruling planets; horary (1–249).
  • Lal Kitab: teva and planet states; the nine debts, graded; the annual chart; remedies in order.
  • Varshaphal (Tajik annual chart), Shadbala, Yogini and Chara dashas.
  • Personal: muhurat with tara and chandra bala, a horoscope from your own Moon sign, transits over the natal chart.
  • Hora (planetary hours) and PNG chart images; vimshottari depth 5 (prana) over ranges up to 31 days.
  • 50 operations in all. Ruling planets, horary and hora also accept publishable keys.

2026-09-25 — Try without signing up, playground, status

API changes

  • The reference's "try it" works without an account, through a shared demo key with a daily allowance.
  • New: the playground, product pages, use cases, accuracy with a downloadable test set, status, request logs and usage alerts in the dashboard, llms.txt, Markdown versions of the docs, and a Postman collection.

2026-09-25 — Public launch

API changes

  • api.astrologics.in and developers.astrologics.in are open to everyone: sign up, get test and live keys, and call all 33 operations. Free plan: 3,000 credits a month and 100 test calls a day.
  • Account emails (sign-up, password reset) are delivered.

2026-09-24 — API core and developer portal

API changes

  • 33 operations in 11 groups under /v1: places and timezones, kundli, dasha, doshas, matchmaking, panchang and muhurat, horoscopes, transits, numerology, chart images, platform.
  • Keys: test (never charged), live and publishable (read-only, locked to origins); exact credit metering; standard rate-limit headers; typed errors with doc_url.

Calculation changes

  • First public engine, engine_version 2026.9.24. KP uses the KP-New ayanamsa (Lahiri − 5′24″); everything else uses Lahiri. Graha drishti houses are counted from the aspecting graha.