SEARCH ASTRO INSIGHT API DOCS
The Natal Transit Timing Weekly 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/weekly
en
Methodology and astrological context for Natal Transit Timing Weekly.
Calculates the precise timing of every transit-to-natal aspect perfection across a full 7-day window. For each transiting planet forming an aspect to a natal planet, this endpoint identifies the exact date and time the aspect becomes exact (perfects) during the week, along with the active orb window during which the aspect is in effect. It is the weekly counterpart to Natal Transit Timing Daily, and the timing-focused counterpart to Natal Transit Weekly.
For each transit-to-natal aspect active during the 7-day period, the response provides:
The transiting planet and the natal planet involved in the aspect
The aspect type (e.g., conjunction, sextile, square, trine, opposition)
The exact perfection date and time — the moment the aspect becomes mathematically exact
The active window — the start and end times during which the aspect is within orb
Aspect strength and directional motion context (direct/retrograde)
Weekly astrological planning — Identify the most significant planetary triggers across an entire week at a glance, with precise timing for each
Event timing — Pinpoint the exact moment a transit perfects to time decisions, launches, or important actions
Predictive astrology workflows — Build weekly transit reports or forecasts that go beyond listing active aspects to showing when each one peaks
Comparative analysis — Use alongside Natal Transit Weekly to enrich aspect listings with perfection timing data
Scheduling tools — Power applications that help users plan their week around astrological windows
Covers a full 7-day window, making it ideal for weekly reports and planning tools — a broader scope than the daily timing variant
Supports filtering via aspectsType (all, major, or none) to control which aspects are included in the analysis
Accepts a complete natal birth profile (date, time, geographic coordinates, and timezone) to compute personalized transit-to-natal aspects
Localization is supported via the Accept-Language header, enabling multi-language responses
Configurable astrological settings via headers: Ayanamsha system, house system, and node type (mean/true) — allowing the results to align with different Western astrological traditions
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 Weekly.
The Natal Transit Timing Weekly 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 Weekly 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 Weekly consumes 1 API credit. The endpoint delivers high performance with an average response time of ~80ms.
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.