Stay current
Change Log & Updates
Track SDK releases, API highlights, and upcoming maintenance so you can schedule upgrades with confidence.
Shadbala and Bhavabala APIs
Two strength endpoints join the Vedic set. Shadbala scores each planet across its six strength sources. Bhavabala scores all twelve houses and ranks them.
What’s Changing?
Two endpoints are available in the Basic Astro package: shadbala and bhavabala. Both take the standard eight birth fields.
shadbala returns one entry per planet with total_shadbala_rupa, total_shadbala_virupa, required_minimum_virupa, strength_percent_of_minimum, an is_strong flag, and a components object holding each contributing bala.
bhavabala returns a houses array with per-house strength, plus a summary carrying strongest_house_id, weakest_house_id and ranked_house_ids_desc.
Why it Matters
Strength is what separates a chart listing from a reading. Placements alone do not tell you which planet or house to lead with. These endpoints return that ranking as numbers, so your product can weight its output instead of treating every factor equally. The is_strong flag and the ranked house list are usable directly in application logic.
How to start
POST the eight birth fields to https://json.astrologyapi.com/v1/shadbala or /v1/bhavabala. No existing response changes.
feature
vedic
api
New transits engine
A rebuilt transits engine adds five endpoints under the Transit package. Tropical transits run daily, weekly and monthly. Natal transits return aspect windows with exact timing.
What’s Changing?
Five endpoints ship in the Transit package: tropical_transits/daily, tropical_transits/weekly, tropical_transits/monthly, natal_transits/daily and natal_transits/weekly.
The tropical endpoints return transit_date, ascendant and a transit_house array. Each item names the planet, its natal_sign, the house it is transiting, and an is_retrograde flag.
The natal endpoints return start_date, end_date, natal_ascendant and a transit_relation array. Each relation pairs a transit_planet with a natal_planet, names the aspect_type, and gives the times the aspect starts and becomes exact.
Why it Matters
Transits are what make an astrology product worth opening more than once. A natal chart never changes, so it cannot carry a daily or weekly experience on its own. These endpoints give you a per-day, per-week or per-month feed. The natal variants return the exact time an aspect becomes precise, which is what a notification or a forecast timeline needs.
How to start
Pick the cadence you need and POST the standard birth fields. Existing chart endpoints are unchanged, so transits can be added alongside what you already call.
feature
western
api
Palmistry APIs
Palm reading is available as 16 endpoints on a dedicated host. Send a palm photo, receive a palm id, then request hand, finger, line and mount analysis against that id.
What’s Changing?
The palmistry endpoints live on https://vision.astrologyapi.com/palmistry, not the JSON host.
Work in two steps. Call get-palm-id with an image_url, which accepts a public URL or a base64 data URL in jpeg, jpg, png or webp up to 5MB. The response carries a palm_id.
Pass that palm_id to the analysis endpoints. These include hand-type, fingers, major-lines, minor-lines, mounts and special-features, alongside reading endpoints for career, money, love, marriage, health and luck.
Why it Matters
Palmistry brings a camera-based reading into products that were limited to birth data. A user who does not know their birth time can still get a reading from a photo. The palm id is issued once per image and reused across every analysis call, so one upload supports as many readings as your product offers.
How to start
Read the palm reading guide at /developers/v1/guides/palm-reading for the full two-step flow with a runnable example, or browse the endpoint reference under Palmistry.
feature
palmistry
api
Pay as you go
Wallet balance can now fund API calls without a subscription. Top up, create an access token, and pay per call across the endpoints your product uses.
What’s Changing?
A subscription is no longer required to call the API. Add balance to your wallet and create an access token from the dashboard.
The access token authenticates with the x-astrologyapi-key header and draws against wallet balance per call. Subscription plans continue to work unchanged, and both models can run on the same account.
Why it Matters
Committing to a plan before you know your call volume is a poor first step. Pay as you go removes that decision from the evaluation stage. It also suits traffic that does not fit a monthly quota, such as seasonal spikes or a feature used by a small share of your users.
How to start
See /developers/v1/guides/pay-as-you-go for the full flow. Per-call credit costs are listed in the pricing catalog at /credits-calculator.
billing
wallet
access-token
MCP servers
An MCP server exposes 109 astrology tools to AI agents and IDEs over the Model Context Protocol. Claude, Cursor and other MCP clients can call chart calculations directly.
What’s Changing?
The Model Context Protocol server publishes 109 tools covering Vedic and Western calculations. Any MCP-compatible client can connect, including Claude and Cursor.
Mint an MCP token from the dashboard. A wallet access token works as the source credential, so an MCP connection does not require a subscription.
Why it Matters
A language model cannot compute planetary positions. Asked directly, it produces numbers that look plausible and are wrong. MCP gives the model a tool that returns computed values, so the model writes the interpretation while the API does the arithmetic.
How to start
See /developers/v1/mcp-server for client setup, and /developers/v1/mcp-server/building-with-llms for agent patterns. To wire tool calls yourself instead, read /developers/v1/guides/llm-grounding.
feature
mcp
ai
AstroChat API
A hosted conversational endpoint answers astrology questions from real chart data. Personalized, compatibility and Western variants are available.
What’s Changing?
Chat runs on its own host: POST https://json-chat.astrologyapi.com/api/chat.
Three variants ship together. Personalized chat answers from a single birth chart, compatibility chat works across two charts, and Western chat answers in the tropical tradition.
Why it Matters
Building a chat layer over an astrology API means solving prompt design, grounding and hallucination control before you ship anything. This endpoint handles that work. Answers are generated from computed chart data rather than from a model recalling training text.
How to start
See /developers/v1/chat-api for request and response formats. Chat authenticates with a wallet access token, covered at /developers/v1/guides/tokens-vs-api-keys.
feature
ai
chat