SEARCH ASTRO INSIGHT API DOCS
The Swamsa Chart Extended API provides detailed Swamsa chart calculations with additional astrological insights, making it ideal for comprehensive Jaimini astrology analysis and report generation.
https://json.astroinsightapi.com/api/v1/chart/jaimini/swamsa/extended
en
hi
ma
Methodology and astrological context for Swamsa Chart Extended.
The Swamsa Chart Extended endpoint is part of the Jaimini astrology system and provides a deeply enriched analysis of the Swamsa chart — one of the most spiritually significant charts in Jaimini Jyotish.
In Jaimini astrology, Swamsa refers to the Navamsa sign occupied by the Atmakaraka — the planet with the highest degree in the natal chart, representing the soul's karmic essence. The Swamsa chart reveals the innermost desires, spiritual inclinations, and the overarching life purpose of an individual. It is considered a window into the soul's journey across lifetimes.
This endpoint generates the extended version of the Swamsa chart using the provided birth data. It goes well beyond a standard Swamsa chart by incorporating multiple advanced layers of Jaimini analysis, offering a comprehensive and nuanced picture of the native's spiritual and karmic blueprint.
The API returns structured JSON containing enriched Swamsa chart data, including:
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
|
| 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 Swamsa Chart Extended.
The Swamsa Chart Extended API provides authentic Jaimini 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 Swamsa Chart Extended 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 Swamsa Chart Extended consumes 1 API credit. The endpoint delivers high performance with an average response time of ~65ms.
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, Hindi, Marathi. 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.