SEARCH ASTRO INSIGHT API DOCS
The Natal Transit Monthly API provides transit related calculations and insights based on Western Astrology astrology data. This endpoint is designed for horoscope platforms, astrology applications, mobile apps, and developer integrations requiring accurate JSON responses and scalable REST API access.
https://json.astroinsightapi.com/api/v1/western/transits/natal/monthly
en
Methodology and astrological context for Natal Transit Monthly.
The Natal Transit Monthly API calculates and returns transit-to-natal planetary aspects across an entire calendar month. For each day of the specified month, it compares the positions of transiting planets against the planets in an individual's natal (birth) chart, producing a comprehensive month-long astrological transit picture.
This endpoint is the monthly counterpart to the Natal Transit Daily and Natal Transit Weekly endpoints, offering a broader temporal view of how current planetary movements interact with a person's natal placements over a full month.
For each day of the requested month, the API returns the active aspects formed between transiting planets and natal planets. Each aspect entry typically includes:
The transiting planet and natal planet involved
The type of aspect formed (e.g., conjunction, opposition, trine, square, sextile)
Aspect strength or orb information
Localized planet and aspect names (based on the Accept-Language header)
The response covers all days of the month in a single call, making it efficient for generating monthly transit calendars or summaries.
Monthly horoscope generation — Build personalized monthly transit reports for users based on their birth data.
Astrological planning tools — Help users identify favorable or challenging periods within a month by highlighting key transit-to-natal aspects.
Transit calendars — Populate day-by-day transit calendars with aspect data for an entire month at once.
Comparative transit analysis — Use alongside the Daily and Weekly endpoints to offer users transit insights at different levels of granularity.
Astrology apps and dashboards — Power monthly overview screens that display a user's most significant planetary influences.
Full-month coverage — Computes transit-to-natal aspects for every day of the given month in a single request, eliminating the need for repeated daily calls.
Aspect filtering — The aspectsType field controls which aspects are included in the response: all returns every aspect, major returns only the most significant aspects (conjunction, opposition, trine, square, sextile), and none can be used to suppress aspect data.
Natal chart anchoring — The birth date, time, and geographic coordinates provided in the request body define the individual's natal chart, which serves as the fixed reference point for all transit comparisons throughout the month.
Ayanamsha support — The X-Ayanamsha header allows the calculation to be performed using different ayanamsha systems, accommodating various Western and Vedic astrological traditions.
House system flexibility — The X-House-Type header lets you specify the house system (e.g., Placidus, Whole Sign, Koch) used in the natal chart calculations.
Node type selection — The X-Node-Type header controls whether the True Node or Mean Node is used for lunar node calculations.
Localization — The Accept-Language header enables localized names for planets, signs, and aspects, supporting multi-language astrology applications.
Payload specifications for JSON request body.
| Parameter | Type | Description & Example |
|---|---|---|
|
day
Required
|
integer |
Day of birth (1–31).
Example:
15
|
|
month
Required
|
integer |
Month of birth (1–12).
Example:
9
|
|
year
Required
|
integer |
Year of birth (e.g., 1994).
Example:
1994
|
|
hour
Required
|
integer |
Hour of birth in 24-hour format (0–23).
Example:
12
|
|
min
Required
|
integer |
Minute of birth (0–59).
Example:
30
|
|
sec
Optional
|
integer |
Second of birth (0–59). Optional. If not provided, it is considered as 0.
Example:
30
|
|
lat
Required
|
float |
Latitude of the birth location.
Example:
28.6139
|
|
lon
Required
|
float |
Longitude of the birth location.
Example:
77.1025
|
|
tzone
Optional
|
float |
Timezone offset from UTC. Optional. If not provided, it is considered as 5.5 (IST).
Example:
5.5
|
|
aspectsType
Optional
|
string |
Aspect type to return. Optional. Default is all. expected. all|major|none.
Example:
all
|
| Header Key | Value / Format | Description |
|---|---|---|
|
Authorization
Required
|
Basic {base64} |
Base64 encoded string of CLIENT_ID:CLIENT_SECRET. |
|
Content-Type
Required
|
application/json |
Specifies JSON payload format in request body. |
|
Accept-Language
Optional
|
en, hi, ta, te... |
Returns localized astrology output. Default: en |
|
X-Ayanamsha
Optional
|
lahiri, raman, krishnamurti... |
Ayanamsha system: lahiri, raman, fagan_bradley, usha_shashi, krishnamurti, djwhal_khul, yukteshwar, jn_bhasin, suryasiddhanta, aryabhata. Default: lahiri |
Explore complementary endpoints in this category.
Comprehensive developer guidance for Natal Transit Monthly.
The Natal Transit Monthly API provides authentic Transit calculations based on Vedic astrology algorithms. It returns structured JSON data containing detailed planetary positions, house calculations, and astrological parameters suitable for Kundli apps, astrology websites, and developer applications.
The Natal Transit Monthly API requires standard Vedic birth details: day, month, year, hour, min, sec, latitude (lat), longitude (lon), and timezone (tzone). All parameters can be passed in the JSON request body.
Each calculation request to Natal Transit Monthly consumes 1 API credit. The endpoint delivers high performance with an average response time of ~96ms.
Authenticate using HTTP Basic Authentication by including your Base64 encoded client_id:client_secret credentials in the Authorization header (Authorization: Basic BASE64(client_id:client_secret)).
Yes! The API supports multiple languages including English. Pass your desired language code (e.g. 'hi' for Hindi, 'ta' for Tamil, 'en' for English) in the Accept-Language request header.
Supported Ayanamshas include NC Lahiri (Default), BV Raman, Krishnamurti (KP), Fagan Bradley, Usha Shashi, Djwhal Khul, Sri Yukteshwar, JN Bhasin, Surya Siddhanta, and Aryabhata. Specify your choice using the X-Ayanamsha header.
The API returns clean JSON UTF-8 output. Successful requests return HTTP 200 OK with the computed data payload. Parameter validation errors return HTTP 422 with actionable error messages.