SEARCH ASTRO INSIGHT API DOCS
The Planetary Friendship API provides astro details related data and calculations using Vedic Astrology principles. This endpoint is designed for astrology applications, kundli generation, horoscope platforms, and developer integrations requiring accurate JSON-based responses and scalable REST API access.
https://json.astroinsightapi.com/api/v1/astro-details/planetary-friendship
en
hi
ma
Methodology and astrological context for Planetary Friendship.
The Planetary Friendship API computes the complete inter-planetary relationship matrix for a native's birth chart in Vedic astrology. In Jyotish, every planet (graha) holds a defined disposition toward every other planet — ranging from deep friendship to bitter enmity — and these relationships directly influence how planetary energies combine, amplify, or suppress each other in a horoscope.
This API goes beyond static, textbook-level planetary relationships. By accepting precise birth details, it calculates both the fixed, universal relationships between planets and the chart-specific, temporary relationships that arise from the actual positions of planets in the native's horoscope. It then synthesizes these two layers into a compound relationship — the definitive inter-planetary disposition for that individual's chart.
The API returns a full relationship matrix covering all major planets (Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, and typically Rahu/Ketu). For each planet pairing, the response provides:
Natural (Naisargika) Relationship — the permanent, universal friendship or enmity between two planets as defined by classical Vedic texts, independent of any chart
Temporary (Tatkalika) Relationship — the chart-specific relationship determined by the relative house positions of the two planets in the native's horoscope (planets in the 2nd, 3rd, 4th, 10th, 11th, and 12th positions from each other are temporary friends; those in the 1st, 5th, 6th, 7th, 8th, and 9th are temporary enemies)
Compound (Panchadhā Maitri) Relationship — the final synthesized relationship derived by combining the natural and temporary relationships, yielding a five-tier scale: Adhi Mitra (bosom friend), Mitra (friend), Sama (neutral), Shatru (enemy), or Adhi Shatru (bitter enemy)
Birth chart (Kundli) interpretation — Providing astrologers and astrology platforms with the full planetary relationship matrix needed to assess how planets in a horoscope interact and modify each other's results
Planetary strength analysis — Determining whether a planet is operating in a friendly or hostile environment within the chart, which directly affects its ability to deliver positive or negative results
Yoga identification — Supporting the detection of planetary combinations (yogas) where the friendship or enmity between participating planets determines the strength and quality of the yoga
Dasha and transit analysis — Evaluating whether a planet running its Mahadasha or transiting a key position is in a friendly or inimical relationship with the chart lord, lagna lord, or other significant planets
Compatibility (Synastry) analysis — Extending the relationship matrix to compare planetary dispositions across two charts for relationship compatibility assessments
Astrology software and apps — Powering the "planetary relationships" module in Jyotish platforms, horoscope generators, and personalized astrology report engines
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 Planetary Friendship.
The Planetary Friendship API provides authentic Astro Details 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 Planetary Friendship 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 Planetary Friendship consumes 1 API credit. The endpoint delivers high performance with an average response time of ~58ms.
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.