SEARCH ASTRO INSIGHT API DOCS
The Natal Transit 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/weekly
en
Methodology and astrological context for Natal Transit Weekly.
The Natal Transit Weekly endpoint provides a comprehensive overview of transit-to-natal planetary aspects spanning a full 7-day window. It compares the positions of transiting planets across the entire week against the fixed planetary positions in an individual's natal (birth) chart, revealing how current celestial movements interact with a person's unique astrological blueprint over the course of the week.
This API calculates and returns all significant planetary aspects formed between transiting planets and natal planets for each day within the current week. By evaluating the week as a whole, it offers a broader astrological perspective than a single-day snapshot — allowing users to see how energies build, peak, and shift across multiple days.
It is the weekly counterpart to the Natal Transit Daily endpoint. While the daily endpoint focuses on aspects active on a specific day, this endpoint aggregates transit-to-natal aspect data across the full 7-day period, giving a holistic view of the week's astrological influences.
The response delivers a structured breakdown of transit-to-natal aspects for each day of the week, typically including:
Transiting planet — the planet currently moving through the sky
Natal planet — the planet in the individual's birth chart being aspected
Aspect type — the angular relationship between the two planets (e.g., conjunction, opposition, trine, square, sextile)
Aspect strength or orb — how exact or wide the aspect is
Day-by-day listing — aspects organized across the 7-day window so users can track how influences evolve throughout the week
The scope of aspects returned is controlled by the aspectsType field, which can be set to return all aspects, only major aspects, or none.
Weekly astrological forecasting — Generate personalized weekly horoscopes or transit reports for individuals based on their birth data
Astrology applications & platforms — Power weekly transit widgets, dashboards, or reports in consumer-facing astrology apps
Personal planning tools — Help users identify favorable or challenging days within the week based on their natal chart interactions
Astrological research — Analyze patterns in transit-to-natal aspect activity over weekly cycles
Comparative analysis — Use alongside the Natal Transit Daily endpoint to drill down from a weekly overview into specific daily details
Full 7-day transit window — Covers the entire current week rather than a single day, providing a complete weekly astrological picture
Natal chart integration — All transit aspects are calculated relative to the individual's personal birth chart, making results unique to each person
Flexible aspect filtering — The aspectsType parameter allows control over whether all aspects, only major aspects, or no aspects are included in the response
Localization support — Planet names, aspect names, and other labels can be returned in different languages via the Accept-Language header
Configurable astrological settings — Supports multiple ayanamsha systems, house systems, and node types, enabling compatibility with various Western astrological traditions
Precise birth data input — Accepts full birth date, time, and geographic coordinates to ensure accurate natal chart calculations
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 Weekly.
The Natal Transit 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 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 Weekly consumes 1 API credit. The endpoint delivers high performance with an average response time of ~107ms.
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.