SEARCH ASTRO INSIGHT API DOCS
The Natal Transit Timing 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/timing/monthly
en
Methodology and astrological context for Natal Transit Timing Monthly.
The Natal Transit Timing Monthly endpoint calculates the precise date and time each transit-to-natal aspect perfects (becomes exact) across a full calendar month, anchored to an individual's natal chart. It is the monthly counterpart to Natal Transit Timing Daily and Natal Transit Timing Weekly, and the timing-focused complement to Natal Transit Monthly — delivering the complete month's aspect perfection schedule in a single call.
Given a person's natal birth data and a target month, this endpoint computes every moment during that month when a transiting planet forms an exact aspect to a natal planet or point. Rather than simply listing which transits are active, it pinpoints the exact perfection time for each aspect — the precise instant the angular relationship between the transiting and natal body reaches its defined degree.
The response provides a structured monthly schedule of transit-to-natal aspect perfections, including:
Transiting planet forming the aspect
Natal planet or point being aspected
Aspect type (e.g., conjunction, sextile, square, trine, opposition, and others depending on the aspectsType filter)
Exact perfection date and time for each aspect within the requested month
Results localized according to the Accept-Language header and adjusted for the specified timezone
Astrological timing and forecasting — Identify the most significant days and times within a month when key natal placements are activated by transiting planets.
Monthly planning tools — Power calendar-style astrology apps that highlight peak transit moments for a user throughout the month.
Comparative transit analysis — Use alongside Natal Transit Monthly to enrich active-transit data with exact perfection timestamps.
Personalized astrology reports — Generate detailed monthly transit reports for clients, showing not just which transits occur but precisely when they peak.
Research and pattern analysis — Study the distribution and clustering of aspect perfections across a month for a given natal chart.
Full-month coverage in one call — Returns all transit-to-natal aspect perfections for the entire calendar month, eliminating the need for multiple daily or weekly requests.
Aspect filtering via aspectsType — Control which aspects are included: all returns every supported aspect type, major (the default) returns only the five major aspects (conjunction, sextile, square, trine, opposition), and none can be used to suppress aspects.
Natal chart anchoring — All transit calculations are relative to the individual's natal chart, derived from the supplied birth date, time, geographic coordinates, and timezone.
Configurable astrological settings — Supports customization of the ayanamsha system, house system, and node type via request headers, allowing the endpoint to serve both Western tropical and other astrological traditions.
Localization support — The Accept-Language header enables localized planet, sign, and aspect names in the response, making it suitable for multi-language applications.
Timezone-aware output — Perfection times are calculated and returned relative to the natal timezone, ensuring accurate local-time scheduling.
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 Timing Monthly.
The Natal Transit Timing 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 Timing 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 Timing Monthly consumes 1 API credit. The endpoint delivers high performance with an average response time of ~82ms.
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.