SoulOSSoulOS API
Getting Started
Overview Accuracy How We Compare Authentication Quick Start Errors Plans & Limits
Birth Chart
POST /v1/chart Request Body Chart Styles Response Planets Houses Vimshottari Dasha Yogas Nakshatra
Deeper Analysis
POST /v1/divisional POST /v1/jaimini POST /v1/dasha POST /v1/timezone MCP Server POST /v1/dosha
Matching
POST /v1/compatibility POST /v1/synastry
Time & Numbers
POST /v1/panchang POST /v1/ankashastra
Help
Support

SoulOS Kundli API

The most accurate Vedic astrology calculation engine available as an API. Built on SoulOS Engine, strictly following Parashar's Brihat Parashar Hora Shastra: Whole Sign houses, Lahiri ayanamsa, Vimshottari Dasha.

Base URL
kundli.soulmapbysahil.in
Protocol
HTTPS · REST · JSON
Ayanamsa
Lahiri (Chitra Paksha)
House System
Whole Sign (Parashar)
Dasha System
Vimshottari (120-year)
Engine
SoulOS Engine

Endpoints at a Glance

Every endpoint takes a JSON body with your api_key and returns the same envelope: status, data, meta. Start with /v1/chart; the others build on the same birth data. Every endpoint is open on every plan.

Machine-readable: OpenAPI 3.1 spec · llms.txt · llms-full.txt: load the spec into Postman, Insomnia, an SDK generator or an AI agent.

EndpointWhat it returns
POST /v1/chartBirth chart: Lagna, planets, houses, nakshatras, 5-level Vimshottari Dasha, 40 yogas, chart SVG
POST /v1/divisional24 divisional charts (D1–D150) with Lagna and planet degrees and a birth-time window
POST /v1/jaiminiJaimini system: Chara Karakas, Karakamsha, Arudha Padas, Rashi Drishti, Argala, Chara Dasha
POST /v1/dashaVimshottari (5 levels), Yogini and Chara Dasha: balance at birth, running periods on any date, timelines
POST /v1/timezoneThe correct UTC offset for any birth: summer time, India war time 1941–45, local mean time before 1906
/mcpMCP server: use every endpoint as tools inside Claude, ChatGPT, Claude Code and Cursor
POST /v1/doshaThe four classical doshas: Mangal, Shrapit, Pitra and Sadhe Sati
POST /v1/compatibilityKundli Milan: 36-guna Ashtakoot matching
POST /v1/synastryGraha-Sthiti overlay: each person’s planets in the other’s houses
POST /v1/panchangPanchang for any date and place: tithi, nakshatra, yoga, karana, vara, festivals
POST /v1/ankashastraAnkashastra (Vedic numerology) from date of birth and name

Accuracy

We check the engine against published charts, not against itself. On 20 November 2026 we ran the birth data of five well-known charts from AstroSage’s celebrity database through the API and compared every result.

ChartBirth (as published)PlaceLargest gap (Lagna + 9 grahas)D1 & D9 signs identicalVimshottari balance matches
Mahatma Gandhi1869-10-02 08:36Porbandar1.6′YesMercury
Jawaharlal Nehru1889-11-14 23:30Allahabad1.2′YesMercury
Indira Gandhi1917-11-19 23:11Allahabad6.2′ (Saturn)YesSun
Swami Vivekananda1863-01-12 06:20Calcutta1.0′YesMoon
Sachin Tendulkar1973-04-24 14:25Mumbai1.1′YesVenus
  • Lagna and planets agree to about 1 arc-minute (one sixtieth of a degree). The one larger gap (Indira Gandhi’s Saturn, 6′) most likely comes from a difference in the other site’s calculation.
  • Chara Karakas, Arudha Padas and Chara Dasha computed from either set of positions are identical. Our one published Jaimini cross-check, Gandhi’s Amatyakaraka is Jupiter, matches.
  • The 16 classical divisional charts are checked at 576,000 points against the frozen rules after every engine change, and the five charts above are a regression suite.

How We Compare

Every feature on every plan, the lowest entry price, and the deepest classical coverage: 24 divisional charts, Jaimini and three dasha systems.

APIFreeEntry paid planDivisional chartsJaiminiDasha systems
SoulOS Kundli API100 calls/day, every endpoint₹499 · 1,000/day (~30,000/mo)24 incl. D81–D150, with degrees + birth-time windowYesVimshottari (5 levels), Yogini, Chara
FreeAstrologyAPI500 calls/day₹1,000 · 50,000/moabout 19 (D2–D60)Not statedVimshottari
VedicAstroAPI14-day trial₹1,499 · 30,000/moYesNot statedYes
AstrologyAPI150 creditsFrom ₹1,500/mo (credit wallet)YesNot statedYes
Prokerala5,000 credits/mo (a kundli ≈ 50 credits)₹999 · 100,000 creditsYesNot statedYes
RoxyAPIPlayground only$39 · 50,000/mo15Not statedVimshottari

Published prices and free plans, November 2026.

Need KP, ready-made PDF reports or Western astrology? Other providers offer those today. Choose SoulOS for classical Parashari and Jaimini depth, with birth-time reliability on every divisional chart.

API Keys

Every request must carry your API key. Pass it in the Authorization header (preferred) or in the JSON body.

Authorization Header
Authorization: Bearer soul_live_<your-key>

Or include api_key directly in the JSON body:

Body Auth
{
  "api_key": "soul_live_<your-key>",
  "dob":     "1987-07-08",
  // ... other fields
}
Register free at kundli.soulmapbysahil.in/dev/register: instant key, no approval needed. Free Plan gives you 100 calls/day to start.

Your First Request

One POST, one response. A complete Vedic birth chart in milliseconds.

cURL

terminal
curl -X POST https://kundli.soulmapbysahil.in/v1/chart \
     -H "Authorization: Bearer soul_live_<YOUR_KEY>" \
     -H "Content-Type: application/json" \
     -d '{
       "dob": "1987-07-08",
       "tob": "05:19:00",
       "lat": "32:47",
       "lon": "74:44",
       "tz":  5.5
     }'

Python

chart.py
import requests

payload = {
    "dob": "1987-07-08",
    "tob": "05:19:00",
    "lat": "32:47",
    "lon": "74:44",
    "tz":  5.5
}
headers = {"Authorization": "Bearer soul_live_<YOUR_KEY>"}

r = requests.post(
    "https://kundli.soulmapbysahil.in/v1/chart",
    json=payload,
    headers=headers
)
data = r.json()["data"]
print(data["basic"]["lagna"])   # → "Gemini"

PHP

chart.php
$response = file_get_contents(
    'https://kundli.soulmapbysahil.in/v1/chart',
    false,
    stream_context_create(['http' => [
        'method'  => 'POST',
        'header'  => "Content-Type: application/json\r\n"
                  . "Authorization: Bearer soul_live_<YOUR_KEY>",
        'content' => json_encode([
            'dob' => '1987-07-08',  'tob' => '05:19:00',
            'lat' => '32:47',     'lon' => '74:44',
            'tz'  => 5.5
        ])
    ]])
);
$chart = json_decode($response, true)['data'];
echo $chart['basic']['lagna'];  // Gemini

JavaScript

chart.js
const res = await fetch("https://kundli.soulmapbysahil.in/v1/chart", {
    method:  "POST",
    headers: {
        "Content-Type":  "application/json",
        "Authorization": "Bearer soul_live_<YOUR_KEY>"
    },
    body: JSON.stringify({
        dob: "1987-07-08",  tob: "05:19:00",
        lat: "32:47",     lon: "74:44",  tz: 5.5
    })
});
const { data } = await res.json();
console.log(data.basic.lagna);   // "Gemini"

Error Codes

Every error returns the same envelope: status: "error", a machine-readable code and, in most cases, a human-readable message. Branch on the HTTP status and code; show message to people.

HTTPCodeMeaningEndpoints
400INVALID_JSONRequest body is not valid JSONAll
400MISSING_FIELDA required field is missing: message names itAll
400INVALID_INPUTA field has the wrong format or range (dob, tob, lat, lon, tz, include …)All
400INVALID_CHARTNone of the requested charts exist/v1/divisional
400INVALID_VARIANTUnknown variant for a chart (e.g. D108)/v1/divisional
401AUTH_FAILEDAPI key missing or not recognisedAll
403AUTH_FAILEDAPI key inactive, suspended, or its plan has expired: message says whichAll
404ENDPOINT_NOT_FOUNDNo endpoint at this pathAll
405METHOD_NOT_ALLOWEDOnly POST (and OPTIONS for CORS) is acceptedAll
422UNKNOWN_NAKSHATRA_OR_RASHIA nakshatra or rashi name was not recognised/v1/compatibility
429RATE_LIMITEDDaily or per-minute limit reached. message says which; wait for the Retry-After header (seconds) on per-minute limitsAll
500ENGINE_ERRORThe calculation failed. Retry once; if it repeats, contact support with the request bodyAll
Error Response
{
  "status":  "error",
  "code":    "MISSING_FIELD",
  "message": "dob is required"
}

Plans & Limits

Every plan gets every endpoint and every feature: all 24 divisional charts, Jaimini, three dasha systems, matching, panchang, doshas and numerology. Plans differ only in volume, speed, licence and support. Each call that passes authentication counts once, however many charts or sections it returns.

PlanCalls / DayCalls / MinutePriceUse
Free10010₹ 0Development and personal projects
Starter1,00030₹ 499 / moCommercial use in a live app · email support
Pro5,00060₹ 2,999 / moCommercial use · priority support · GST invoice
EnterpriseCustomCustomCustomCustom volume and support

Rate-Limit Headers

Every authenticated response carries X-RateLimit-Limit-Day, X-RateLimit-Remaining-Day and X-RateLimit-Limit-Minute, so your app can pace itself.

Over a limit, the API returns HTTP 429 with code: "RATE_LIMITED". For the per-minute limit, wait the number of seconds in the Retry-After header. The daily counter resets at midnight IST. Calls refused for the per-minute limit do not use up your daily quota.

POST /v1/chart

Calculates a complete Vedic birth chart. Returns planets in all 12 signs, Whole Sign houses, Vimshottari Dasha timeline, Yogas, Nakshatra details, and Avkahada Chakra.

POST https://kundli.soulmapbysahil.in/v1/chart

Request Body

FieldTypeStatusDescription
dob string Required Date of birth in YYYY-MM-DD format.
Example: 1987-07-08
tob string Required Time of birth in HH:MM or HH:MM:SS format (24-hour).
Example: 05:19:00
lat string Required Latitude: decimal degrees or DMS notation.
Decimal: 32.7833  ·  DMS: 32:47
lon string Required Longitude: decimal degrees or DMS notation.
Decimal: 74.7333  ·  DMS: 74:44
tz float Optional UTC offset in hours. Defaults to 5.5 (IST).
Example: 5.5 for IST, -5 for EST
name string Optional Person's name: echoed back in the response.
dasha_depth integer Optional Depth of the Vimshottari Dasha tree. Default 5 (all levels).
1 = Mahadasha only  ·  2 = +Antardasha  ·  3 = +Pratyantar  ·  4 = +Sookshma  ·  5 = +Prana (full ~66K entries)
chart boolean Optional Include a rendered North Indian birth chart SVG in the response. Default false.
When true — data.chart_svg contains the full inline SVG string. meta.chart_included confirms whether it was generated. Omit or pass false to keep the response lean. The Lagna box shows the Lagna degree. For divisional chart SVGs (D9, D10, D60 and the rest) use POST /v1/divisional with svg: true.
chart_theme string Optional The chart’s look: cosmic (default), classic or minimal. Pass a list, e.g. ["cosmic","minimal"], to get several at once in data.chart_svgs, ideal for sites with light and dark modes. See Chart Styles.
chart_labels string Optional numbers (default, traditional sign numbers) or names (Ari, Tau, Gem…), friendlier for beginners.
chart_title boolean Optional Show the chart’s name above it, e.g. “D1 · Rashi”. Default true; pass false when your page has its own heading.
include array Optional Array of optional response expansions.
"insights": adds data.insights: a complete natal interpretation built from Dr. Kohli's Parashar knowledge base. Includes a synthesis (flowing combined reading), per-planet interpretations (in sign + in house), house lord placements, Moon nakshatra, conjunctions, and current Mahadasha meaning.
Example: "include": ["insights"]
Combine with name to personalise the text with the person's name.
lang string Optional Language code for data.insights interpretation text. Default en (English).
Supported: en English  ·  hi Hindi  ·  hg Hinglish  ·  ne Nepali  ·  ur Urdu  ·  ta Tamil  ·  te Telugu  ·  ml Malayalam  ·  pa Punjabi
Falls back to English if a translation is incomplete. Only applies when "insights" is included in include.
api_key string Optional API key if not passing via Authorization header.

Chart Styles

Your chart should look like it belongs on your site. A square, traditional North Indian kundli, readable on any phone, in three styles. Every planet gets its degree with retrograde and combust marks, the Lagna glows, and each chart carries its name. Crowded houses rearrange themselves, so even a D2 with all nine planets in two houses stays clean.

Choose with chart_theme, chart_labels (numbers or names) and chart_title on /v1/chart or /v1/divisional. Running light and dark modes? Ask for ["cosmic","minimal"] and switch with your theme.


Complete Response

Below is the actual verified response for 08 Jul 1987 · 05:19 IST · Jammu, J&K: cross-verified against AstroSage.

JSON Basic Info

response.json → data.basic
"basic": {
  "lagna":          "Gemini",         // Ascendant sign
  "lagna_lord":     "Mercury",
  "rashi":          "Scorpio",        // Moon sign
  "rashi_lord":     "Mars",
  "nakshatra":      "Anuradha",       // Moon nakshatra
  "nakshatra_pada": 2,
  "nakshatra_lord": "Saturn",
  "dob":            "1987-07-08",
  "tob":            "05:19:00",
  "latitude":       32.783,
  "longitude":      74.733,
  "timezone":       5.5,
  "ayanamsa":       "Lahiri"
}

Planets

All 9 Vedic grahas, Sun through Ketu, including outer planets for reference. Each planet includes sign, degree within sign, absolute ecliptic longitude, retrograde flag, and combustion flag.

response.json → data.planets
"planets": {

  "sun": {
    "sign":        "Gemini",
    "sign_num":    3,
    "degree":      21.6423,      // degrees within sign
    "longitude":   81.6423,      // absolute ecliptic longitude
    "retrograde":  false
  },

  "moon": {
    "sign":        "Scorpio",
    "sign_num":    8,
    "degree":      7.3559,
    "longitude":   217.3559,
    "retrograde":  false,
    "combust":     false
  },

  "mercury": {
    "sign":        "Gemini",
    "sign_num":    3,
    "degree":      15.8020,
    "longitude":   75.8020,
    "retrograde":  true,          // ← Retrograde
    "combust":     true           // ← Combust
  },

  "venus": {
    "sign":        "Gemini",
    "sign_num":    3,
    "degree":      8.9666,
    "longitude":   68.9666,
    "retrograde":  false,
    "combust":     false
  },

  "mars": {
    "sign":        "Cancer",
    "sign_num":    4,
    "degree":      7.1437,
    "longitude":   97.1437,
    "retrograde":  false,
    "combust":     true           // ← Combust
  },

  "jupiter": {
    "sign":        "Aries",
    "sign_num":    1,
    "degree":      3.1922,
    "longitude":   3.1922,
    "retrograde":  false
  },

  "saturn": {
    "sign":        "Scorpio",
    "sign_num":    8,
    "degree":      22.2013,
    "longitude":   232.2013,
    "retrograde":  true           // ← Retrograde
  },

  "rahu": {
    "sign":        "Pisces",
    "sign_num":    12,
    "degree":      12.8579,
    "longitude":   342.8579,
    "retrograde":  true           // always retrograde
  },

  "ketu": {
    "sign":        "Virgo",
    "sign_num":    6,
    "degree":      12.8579,
    "longitude":   162.8579,
    "retrograde":  true           // always retrograde (180° from Rahu)
  }

}

Houses

Whole Sign system per Parashar BPHS. Each house occupies exactly one sign. House 1 starts at Lagna sign degree 0.

response.json → data.houses
"houses": {
  "1":  { "sign": "Gemini",      "sign_num": 3,  "longitude": 60  },  // Tanu: Self
  "2":  { "sign": "Cancer",      "sign_num": 4,  "longitude": 90  },  // Dhana: Wealth
  "3":  { "sign": "Leo",         "sign_num": 5,  "longitude": 120 },  // Sahaja: Siblings
  "4":  { "sign": "Virgo",        "sign_num": 6,  "longitude": 150 },  // Sukha: Home
  "5":  { "sign": "Libra",        "sign_num": 7,  "longitude": 180 },  // Putra: Children / Intelligence
  "6":  { "sign": "Scorpio",      "sign_num": 8,  "longitude": 210 },  // Ari: Enemies / Disease
  "7":  { "sign": "Sagittarius", "sign_num": 9,  "longitude": 240 },  // Yuvati: Partnership
  "8":  { "sign": "Capricorn",    "sign_num": 10, "longitude": 270 },  // Randhra: Longevity
  "9":  { "sign": "Aquarius",     "sign_num": 11, "longitude": 300 },  // Dharma: Fortune
  "10": { "sign": "Pisces",       "sign_num": 12, "longitude": 330 },  // Karma: Career
  "11": { "sign": "Aries",        "sign_num": 1,  "longitude": 0   },  // Labha: Gains
  "12": { "sign": "Taurus",       "sign_num": 2,  "longitude": 30  }   // Vyaya: Liberation
}

Vimshottari Dasha: All 5 Levels

The only Vedic astrology API that returns all 5 levels of Vimshottari Dasha pre-calculated with exact dates. No need to compute sub-periods yourself. Control response size with dasha_depth.

5 levels, all pre-calculated. Most APIs stop at Antardasha (level 2). We give you Mahadasha → Antardasha → Pratyantar → Sookshma → Prana with exact start/end dates at every level. dasha_depth=5 = default. Use dasha_depth=2 if you only need MD+AD.

JSON Top-level structure

response.json → data.dasha
"dasha": {
  "system":  "Vimshottari",
  "depth":   5,                       // levels calculated in timeline

  "balance_at_birth": {
    "planet":          "Saturn",       // nakshatra lord at birth
    "years_remaining": 2.41,          // years of Saturn MD remaining at DOB
    "ends":            "1989-10-22"    // exact date first MD period ends
  },

  "current": {                         // always 5 levels regardless of depth param
    "mahadasha":  { "planet": "Venus",   "start": "2024-10-22", "end": "2044-10-22" },
    "antardasha": { "planet": "Venus",   "start": "2024-10-22", "end": "2028-02-21" },
    "pratyantar": { "planet": "Saturn",  "start": "2026-01-14", "end": "2026-08-30" },
    "sookshma":   { "planet": "Rahu",    "start": "2026-04-04", "end": "2026-05-22" },
    "prana":      { "planet": "Mercury", "start": "2026-04-28", "end": "2026-05-03" }
  },

  "timeline": [                        // 9 Mahadashas, each nested to dasha_depth
    {
      "planet": "Saturn", "years": 2.41, "start": "1987-07-08", "end": "1989-10-22",
      "antardasha": [                  // 9 Antardashas
        {
          "planet": "Saturn", "years": 0.3823, "start": "1987-07-08", "end": "1987-11-19",
          "pratyantar": [              // 9 Pratyantars
            {
              "planet": "Saturn", "years": 0.0607, "start": "1987-07-08", "end": "1987-08-30",
              "sookshma": [            // 9 Sooksmas
                {
                  "planet": "Saturn", "years": 0.009643, "start": "1987-07-08", "end": "1987-07-12",
                  "prana": [          // 9 Pranas: hours to days
                    { "planet": "Saturn",  "start": "1987-07-08", "end": "1987-07-09" },
                    { "planet": "Mercury", "start": "1987-07-09", "end": "1987-07-09" }
                    // ... 7 more
                  ]
                }
                // ... 8 more sooksmas
              ]
            }
            // ... 8 more pratyantars
          ]
        }
        // ... 8 more antardashas
      ]
    }
    // ... 8 more mahadashas
  ]
}

Depth reference

dasha_depthLevels returnedTotal entriesUse case
1Mahadasha9Quick lookup, dashboards
2MD + Antardasha81Most apps: years-level planning
3+ Pratyantar729Month-level precision
4+ Sookshma6,561Week-level precision
5+ Prana (default)~66,430Day-level precision, full pre-calculation

The current block always returns all 5 levels regardless of dasha_depth.


Yogas

40 Parashari Yogas checked per Brihat Parashar Hora Shastra across 7 categories. Only yogas present in the chart are returned. If no yoga is present, the array is empty.

Category Yogas
Pancha Mahapurusha Hamsa, Malavya, Ruchaka, Sasa, Bhadra
Raja Kendra-Trikona, Dharma-Karma Adhipati, Neecha Bhanga Raja, Parijata
Dhana Dhana, Lakshmi, Akhand Samrajya
Special Gajakesari, Budhaditya, Chandra-Mangal, Amala, Vasumati, Chatussagara, Parvata, Kahala, Chamara, Shankha, Saraswati, Kalanidhi, Kusuma, Mahabhagya, Pushkala, Musala
Chandra Sunapha, Anapha, Durudhura, Kemdrum, Shakata, Adhi
Surya Vesi, Vosi, Ubhayachari
Viparita Raja Harsha, Sarala, Vimala
response.json → data.yogas
"yogas": [
  {
    "name":              "Budhaditya Yoga",
    "category":         "Special",
    "nature":           "benefic",          // "benefic" or "challenging"
    "present":          true,           // always true: absent yogas are not returned
    "description":      "Sun and Mercury in the same sign. Sharp intellect, eloquence, and analytical precision.",
    "planets_involved": ["Sun", "Mercury"],
    "house_positions":  [1]             // houses where planets forming yoga sit
  }
  // only actually present yogas appear here. Empty array [] if none
]

Nakshatra & Avkahada

Nakshatra data for Moon and Sun, plus the full Avkahada Chakra (Varna, Gana, Nadi, Yoni, Vasya).

response.json → data.nakshatras + data.avkahada
"nakshatras": {
  "moon": {
    "name":  "Anuradha",
    "lord":  "Saturn",
    "pada":  2,
    "index": 17
  },
  "sun": {
    "name":  "Ardra",
    "lord":  "Rahu",
    "pada":  4,
    "index": 6
  }
},

"avkahada": {
  "varna":  "Vaishya",      // social classification
  "gana":   "Manushya",     // nature: Deva / Manushya / Rakshasa
  "nadi":   "Madhya",       // Adi / Madhya / Antya
  "yoni":   "Mriga",        // animal symbol
  "vasya":  "Manav"         // compatibility group
}

POST /v1/divisional

Divisional (varga) charts: 24 charts in one endpoint: the 16 Shodashavarga charts of BPHS, the extended Parashari charts D5, D6, D8 and D11, and the higher charts D81, D108, D144 and D150. Every chart returns the Lagna degree and every planet’s degree inside the chart, plus a birth-time window that tells you how far the birth time can be off before the chart’s Lagna changes sign.

All 24 charts are available on every plan, including Free.

POST https://kundli.soulmapbysahil.in/v1/divisional

Request Parameters

FieldTypeRequiredDescription
api_keystringRequiredYour API key
dobstringRequiredDate of birth: YYYY-MM-DD
tobstringRequiredTime of birth: HH:MM or HH:MM:SS (24-hour). Send seconds when you have them; the higher charts change sign within a minute.
latfloatRequiredLatitude of birth place (decimal degrees)
lonfloatRequiredLongitude of birth place (decimal degrees)
tzfloatOptionalUTC offset (default 5.5 for IST)
chartstring | arrayOptionalWhich chart(s) to compute. Default "D9". Single: "D9". Several: ["D6","D9"]. The D is optional ("9" works). Groups: "all", "shodashavarga", "extended", "higher".
variantsobjectOptionalPick a calculation variant where one exists. Today only D108: {"D108": "d9_then_d12"} (default) or {"D108": "d12_then_d9"}.
chart_themestringOptionalLook of the SVGs: cosmic (default), classic or minimal, or a list for several at once (chart_svgs). Also chart_labels (numbers or names) and chart_title (default true, e.g. “D9 · Navamsha”). See Chart Styles.
svgbooleanOptionalWhen true, each chart also returns chart_svg: a North Indian chart with the Lagna degree and planet degrees drawn in. Default false.

Available Charts

CodeNamePart sizeRead for
Shodashavarga: the 16 charts of BPHS Ch. 6
D1Rashi1 sign (30°)Natal chart: body, mind, core personality
D2Hora15°Wealth, financial potential
D3Drekkana10°Siblings, courage, initiative
D4Chaturthamsha7°30′Fortune, property, fixed assets
D7Saptamsha4°17′Children, progeny, creative output
D9Navamsha3°20′Marriage, inner dharma, soul purpose
D10Dashamsha3°Career, profession, public standing
D12Dwadashamsha2°30′Parents, ancestral lineage
D16Shodashamsha1°52′30″Vehicles, comforts, conveyances
D20Vimsamsha1°30′Spiritual practice, worship, sadhana
D24Siddhamsha1°15′Education, learning, knowledge
D27Nakshatramsha1°6′40″Strength, vitality, innate capacity
D30Trimsamshaunequal 5–8°Misfortunes, suffering, health challenges
D40Khavedamsha45′Maternal lineage, auspicious effects
D45Akshavedamsha40′Paternal lineage, all-life analysis
D60Shashtiamsha30′Past life karma, deepest soul imprints
Extended Parashari charts
D5Panchamsha NEW6°Fame, power, authority, past-life merit
D6Shashthamsha NEW5°Health, disease, enemies, debts
D8Ashtamsha NEW3°45′Longevity, sudden events, accidents
D11Rudramsha NEW2°43′38″Gains, and destruction or death (Jaimini use)
Higher charts: need a birth time accurate to the minute
D81Nava-Navamsha NEW22′13″Fine reading of the Navamsha: marriage, dharma
D108Ashtottaramsha NEW16′40″Deep karma, spiritual evolution
D144Dwadash-Dwadashamsha NEW12′30″Fine reading of parents and lineage
D150Nadiamsha NEW12′Nadi readings: finest division of a sign

How the New Charts Are Calculated

The 16 Shodashavarga charts follow BPHS Ch. 6 (D30 uses the unequal Parashari Trimsamsha). The rules for the newer charts are below. Each response also returns the rule it used in meta.method.

ChartRule
D5Odd signs: Aries, Aquarius, Sagittarius, Gemini, Libra. Even signs: Taurus, Virgo, Pisces, Capricorn, Scorpio.
D6Odd signs count from Aries, even signs from Libra.
D8Movable signs from Aries, fixed signs from Sagittarius, dual signs from Leo.
D11Count the sign’s number backward from Aries; the 11 parts start from the sign you land on (Gemini → Aquarius, Scorpio → Virgo).
D81Navamsha of the Navamsha: the D9 rule applied to the D9 longitude.
D108Two variants. d9_then_d12 (default): Dwadashamsha of the Navamsha. d12_then_d9: Navamsha of the Dwadashamsha. Choose with variants.
D144Dwadashamsha of the Dwadashamsha: the D12 rule applied to the D12 longitude.
D150Odd signs count forward from Aries, even signs backward from Pisces.

Lagna and Planet Degrees

Every chart returns the degree of the Lagna and of each planet inside its sign in that chart. The degree is the position inside the part, stretched to a full 30°: (degree in sign − part start) ÷ part size × 30. For equal parts this is the same as (degree in sign × D) mod 30, the convention used by Jagannatha Hora. For D81, D108 and D144 the second division is applied to the first chart’s longitude.

Birth-Time Window

The finer the chart, the faster its Lagna changes. In D1 the Lagna holds a sign for about two hours; in D150 it can change in under a minute. lagna.birth_time_window tells you, for this birth, how many minutes earlier or later the time could be before the chart’s Lagna moves to another sign. It uses the real speed of the Ascendant at that moment and place from SoulOS Engine, not an average.

Show a chart’s Lagna-based reading only when reliability is high or medium, unless the birth time has been verified (for example from a hospital record). Planet signs in the higher charts are less sensitive than the Lagna, because planets move far slower than the Ascendant.

Request Example

POST /v1/divisional: single chart
{
  "api_key": "your_api_key",
  "dob":     "1987-07-08",
  "tob":     "19:25",
  "lat":     30.7333,
  "lon":     76.7794,
  "tz":      5.5,
  "chart":   "D9"
}
POST /v1/divisional: several charts, a D108 variant and SVGs
{
  "api_key":  "your_api_key",
  "dob":      "1987-07-08",
  "tob":      "19:25",
  "lat":      30.7333,
  "lon":      76.7794,
  "tz":       5.5,
  "chart":    ["D6", "D9", "D108", "D150"],
  "variants": { "D108": "d12_then_d9" },   // optional
  "svg":      true                         // optional: adds chart_svg to each chart
}

Response Structure

200 OK: D9 response (abbreviated)
{
  "status": "success",
  "data": {
    "D9": {
      "meta": {
        "D":      9,
        "name":   "Navamsha",
        "group":  "shodashavarga",
        "desc":   "Marriage, inner dharma, soul purpose",
        "method": "Fire from Aries, earth from Capricorn, air from Libra, water from Cancer (3°20' each)"
      },
      "lagna": {
        "sign":       "Libra",
        "sign_num":   7,
        "lord":       "Venus",
        "degree":     20.0826,
        "degree_dms": "20°04'57\"",
        "birth_time_window": {
          "earlier_minutes": 8.81,
          "later_minutes":   4.35,
          "reliability":     "low"
        }
      },
      "planets": {
        "sun": {
          "sign":       "Aries",
          "sign_num":   1,
          "degree":     19.8197,
          "degree_dms": "19°49'11\"",
          "house":      7,
          "retrograde": false,
          "combust":    false
        },
        "moon": { }   // same structure: mars, mercury, jupiter, venus, saturn, rahu, ketu follow
      }
    }
  },
  "meta": {
    "engine":       "SoulOS Engine v1.0",
    "varga_engine": "VargaEngine 2.0",
    "ayanamsa":     "Lahiri",
    "charts":       ["D9"],
    "ignored":      [],
    "failed":       [],
    "lagna_speed_deg_per_day": 364.6562,
    "ms":           8
  }
}

Response Fields

FieldTypeDescription
data.{D}.meta.DintDivisional number (9 for D9)
data.{D}.meta.namestringSanskrit name, e.g. "Navamsha"
data.{D}.meta.groupstringshodashavarga, extended or higher
data.{D}.meta.descstringArea of life this chart is read for
data.{D}.meta.methodstringThe exact rule used to place signs in this chart
data.{D}.meta.variantstringD108 only: which variant was used
data.{D}.lagna.signstringLagna (ascendant) sign in this chart
data.{D}.lagna.sign_numintLagna sign number 1–12
data.{D}.lagna.lordstringLord of the Lagna sign
data.{D}.lagna.degreefloatLagna degree inside its sign in this chart, 0–30
data.{D}.lagna.degree_dmsstringSame degree as text, e.g. 20°04'57"
data.{D}.lagna.birth_time_window.earlier_minutesfloatHow many minutes earlier the birth could be before this chart’s Lagna changes sign
data.{D}.lagna.birth_time_window.later_minutesfloatHow many minutes later the birth could be before this chart’s Lagna changes sign
data.{D}.lagna.birth_time_window.reliabilitystringhigh (15+ min either way), medium (5+), low (1+), very_low (under 1 min)
data.{D}.planets.{name}.signstringPlanet’s sign in this chart
data.{D}.planets.{name}.sign_numintSign number 1–12
data.{D}.planets.{name}.degreefloatPlanet’s degree inside its sign in this chart, 0–30
data.{D}.planets.{name}.degree_dmsstringSame degree as text
data.{D}.planets.{name}.houseintHouse from this chart’s Lagna (1–12)
data.{D}.planets.{name}.retrogradeboolRetrograde at birth
data.{D}.planets.{name}.combustboolCombust at birth
data.{D}.chart_svgstringNorth Indian chart SVG: only when svg: true
meta.chartsarrayCharts returned, in order
meta.ignoredarrayChart names that were not recognised (the rest of the request still runs)
meta.failedarrayCharts that failed to compute (normally empty)
meta.lagna_speed_deg_per_dayfloatSpeed of the natal Lagna at birth, used for the birth-time window

Errors

An unknown chart name is skipped and listed in meta.ignored; if nothing valid is left you get 400 INVALID_CHART. An unknown variant returns 400 INVALID_VARIANT.

  • One SoulOS Engine call is made per request however many charts you ask for: "all" costs the same as "D9"
  • House numbers are counted from the chart’s own Lagna: ((planet_sign − lagna_sign + 12) % 12) + 1
  • For gochar (transit) over natal D9, call this endpoint with today’s date and time and compare with the stored natal chart on your side
  • The response is built to paste straight into an AI prompt for Vedic interpretation. See the “Copy to AI” button on the freekundli.in result page

POST /v1/jaimini

The Jaimini system in one call: Chara Karakas, Karakamsha, Arudha Padas, Rashi Drishti (sign aspects), Argala and Chara Dasha. Everything is computed in one engine call, so asking for all six sections costs the same as asking for one. Open on all plans.

POST https://kundli.soulmapbysahil.in/v1/jaimini

Request Parameters

FieldTypeRequiredDescription
api_keystringRequiredYour API key
dobstringRequiredDate of birth: YYYY-MM-DD
tobstringRequiredTime of birth: HH:MM or HH:MM:SS (24-hour)
latfloatRequiredLatitude of birth place (decimal degrees)
lonfloatRequiredLongitude of birth place (decimal degrees)
tzfloatOptionalUTC offset (default 5.5 for IST)
includearrayOptionalSections to return. Any of karakas, karakamsha, arudha, drishti, argala, chara_dasha. Default: all.
karaka_schemeintOptional8 (default: includes Rahu, as in BPHS and Jagannatha Hora) or 7 (Sun to Saturn only).
exaltation_adjustmentboolOptionalChara Dasha: add 1 year when the sign lord is exalted, take 1 away when debilitated. Default true.
datestringOptionalDate used to mark the running Chara Dasha. YYYY-MM-DD. Default: today (IST).

What Each Section Returns

SectionWhat it isHow it is calculated
karakasThe 8 (or 7) Chara Karakas: Atmakaraka (self) to Darakaraka (spouse)Planets ranked by degree inside their sign, highest first. Rahu counts backward (30° − its degree). Ketu is never a karaka.
karakamshaThe Atmakaraka’s Navamsha sign, with every planet’s house from it in D1 and D9, and the Ishta Devata sign (12th from Karakamsha in D9)Uses the same D9 engine as /v1/divisional
arudhaArudha Padas A1 (Arudha Lagna) to A12 (Upapada) for all 12 housesCount from the house to its lord, then the same count again from the lord. If that lands in the 1st or 7th from the house, take the 10th from there.
drishtiRashi Drishti: which signs, houses and planets each planet aspectsMovable signs aspect fixed signs (except the next sign), fixed aspect movable (except the previous sign), dual signs aspect each other.
argalaArgala (intervention) on each of the 12 houses, and whether it standsBPHS: planets in the 2nd, 4th, 11th (and 5th) give argala, blocked by the 12th, 10th, 3rd (and 9th). Two or more malefics in the 3rd also give argala. An argala stands when its planets outnumber the blockers.
chara_dashaChara Dasha: sign periods for two full cycles, each with 12 antardashas, plus the period running on dateK.N. Rao method: starts from the Lagna sign; runs forward if the 9th sign is Aries, Taurus, Gemini, Libra, Scorpio or Sagittarius, otherwise backward. Years = count from the sign to its lord − 1 (lord in its own sign = 12). Second cycle = 12 − first-cycle years. Each period splits into 12 equal antardashas, the last one being the period’s own sign.
Scorpio and Aquarius have two lords (Mars and Ketu, Saturn and Rahu). Arudha and Chara Dasha pick the stronger one in this order: if one lord sits in the sign, take the other; then the lord with more planets beside it; then the exalted lord; then the lord in a dual sign over fixed over movable; then the higher degree. The choice and the reason are returned in lord and lord_choice.

Request Example

POST /v1/jaimini
{
  "api_key":  "your_api_key",
  "dob":      "1987-07-08",
  "tob":      "19:25",
  "lat":      30.7333,
  "lon":      76.7794,
  "tz":       5.5,
  "include":  ["karakas", "arudha", "chara_dasha"],   // optional: default: all six
  "karaka_scheme": 8                                // optional: 8 (default) or 7
}

Response Structure

200 OK: abbreviated (1987-07-08 19:25 Mohali)
{
  "status": "success",
  "data": {
    "lagna": {"sign": "Sagittarius", "degree": 22.2314},
    "karakas": [
      { "code": "AK", "karaka": "Atmakaraka", "signifies": "Self, soul", "planet": "sun", "sign": "Gemini", "degree": 22.2022, "karaka_degree": 22.2022 }
    ],   // then AmK, BK, MK, PiK, PK, GK, DK
    "karakamsha": {
      "atmakaraka": "sun",
      "sign": "Aries",
      "sign_num": 1,
      "lord": "mars",
      "house_from_lagna_d1": 5,
      "planets_in_karakamsha_d9": ["sun", "jupiter", "ketu"],
      "ishta_devata": { "sign": "Pisces", "planets_d9": [], "lord": "jupiter" }
    },   // plus houses_from_karakamsha_d1 / _d9 for every planet
    "arudha": {
      "A1": { "name": "Arudha Lagna (AL)", "sign": "Leo", "house_from_lagna": 9, "lord": "jupiter", "exception": null },
      "A12": { "name": "Upapada (UL)", "sign": "Cancer", "house_from_lagna": 8, "lord": "ketu", "lord_choice": "sign type (dual > fixed > movable)" }
    },   // A1 … A12
    "drishti": { "signs": { }, "planets": { } },
    "argala": { },   // houses 1–12
    "chara_dasha": {
      "direction": "reverse",
      "ninth_sign": "Leo",
      "current": {"mahadasha": {"sign": "Gemini", "start": "2021-07-08", "end": "2033-07-08", "cycle": 1}, "antardasha": {"sign": "Sagittarius", "start": "2026-07-08", "end": "2027-07-08"}},
      "timeline": [
        { "sign": "Sagittarius", "cycle": 1, "years": 4, "start": "1987-07-08", "end": "1991-07-08", "lord": "jupiter", "lord_sign": "Aries", "adjustment": 0, "antardasha": [ ] }
      ]
    }
  },
  "meta": { "jaimini_engine": "JaiminiEngine 1.0", "karaka_scheme": 8, "included": ["karakas", "karakamsha", "arudha", "drishti", "argala", "chara_dasha"], "date": "2026-11-20", "ms": 8 }
}
  • Only the 9 grahas are used: Uranus, Neptune and Pluto play no part in Jaimini
  • Houses are whole signs from the Lagna, the same as /v1/chart
  • Chara Dasha has no balance at birth: the first period starts on the date of birth and runs in full
  • Jaimini schools differ on details. Every choice that has a school-dependent alternative is either an option above or reported in the response (lord_choice, adjustment, method)

POST /v1/dasha

Three dasha systems in one call: Vimshottari (1–5 levels, Mahadasha to Prana), Yogini (36-year cycle with antardashas) and Jaimini Chara Dasha. Each returns the balance at birth, the periods running on any date you choose, and the full timeline. Open on all plans.

POST https://kundli.soulmapbysahil.in/v1/dasha

Request Parameters

FieldTypeRequiredDescription
api_keystringRequiredYour API key (or Authorization: Bearer)
dob / tobstringRequiredDate (YYYY-MM-DD) and time (HH:MM or HH:MM:SS) of birth
lat / lonfloatRequiredBirth place in decimal degrees
tzfloatOptionalUTC offset (default 5.5)
systemsarrayOptionalAny of vimshottari, yogini, chara. Default: all three.
depthintOptionalVimshottari timeline levels 1–5 (default 3). The running chain in current always has all 5 levels.
datestringOptionalDate for the running periods: YYYY-MM-DD. Default: today (IST). Use any past or future date.
timelineboolOptionalfalse returns only the moon, balance at birth and running periods (about 2 KB: ideal for a “today” widget). Default true.

How Each System Is Calculated

SystemRule
Vimshottari120-year cycle from the Moon’s nakshatra lord. The birth Mahadasha is laid out from its true start before birth, so the antardasha running at birth is the real one (not a squeezed copy). Every boundary is computed from the cycle start, so dates are identical whatever depth you ask for.
Yogini8 Yoginis (Mangala 1 yr … Sankata 8 yrs), 36-year cycle. Starting Yogini = (Moon’s nakshatra number + 3) mod 8. Antardashas start from the Mahadasha Yogini; length = MD years × AD years ÷ 36.
CharaJaimini sign dasha, K.N. Rao method: the same engine as /v1/jaimini.

Dates: 1 year = 12 months, fractional months in 30-day units (stated in meta.year_rule).

Request Example

POST /v1/dasha
{
  "api_key":  "your_api_key",
  "dob":      "1987-07-08",
  "tob":      "19:25",
  "lat":      30.7333,
  "lon":      76.7794,
  "tz":       5.5,
  "systems":  ["vimshottari", "yogini", "chara"],   // optional: default all three
  "date":     "2026-11-20",                         // optional: default today (IST)
  "timeline": false                                 // optional: false = only what is running now
}

Response Structure

200 OK: timeline: false (1987-07-08 19:25 Mohali)
{
  "status": "success",
  "data": {
    "moon": {
      "sign": "Scorpio",
      "degree": 15.8997,
      "nakshatra": "Anuradha",
      "pada": 4,
      "lord": "Saturn"
    },
    "vimshottari": {
      "system": "Vimshottari",
      "depth": 3,
      "balance_at_birth": {
        "planet": "Saturn",
        "years_remaining": 1.09,
        "ends": "1988-08-11"
      },
      "current": {
        "mahadasha": {
          "planet": "Venus",
          "start": "2012-08-11",
          "end": "2032-08-11"
        },
        "antardasha": {
          "planet": "Saturn",
          "start": "2025-06-11",
          "end": "2028-08-11"
        },
        "pratyantar": {
          "planet": "Venus",
          "start": "2026-07-29",
          "end": "2027-02-09"
        },
        "sookshma": {
          "planet": "Jupiter",
          "start": "2026-11-05",
          "end": "2026-12-01"
        },
        "prana": {
          "planet": "Venus",
          "start": "2026-11-17",
          "end": "2026-11-22"
        }
      }
    },
    "yogini": {
      "system": "Yogini",
      "cycle_years": 36,
      "balance_at_birth": {
        "yogini": "Bhramari",
        "planet": "Mars",
        "years_remaining": 0.2301,
        "ends": "1987-10-01"
      },
      "current": {
        "mahadasha": {
          "yogini": "Bhadrika",
          "planet": "Mercury",
          "start": "2023-10-01",
          "end": "2028-10-01"
        },
        "antardasha": {
          "yogini": "Sankata",
          "planet": "Rahu",
          "start": "2026-03-31",
          "end": "2027-05-11"
        }
      }
    },
    "chara": {
      "system": "Jaimini Chara Dasha",
      "direction": "reverse",
      "ninth_sign": "Leo",
      "current": {
        "mahadasha": {
          "sign": "Gemini",
          "start": "2021-07-08",
          "end": "2033-07-08",
          "cycle": 1
        },
        "antardasha": {
          "sign": "Sagittarius",
          "start": "2026-07-08",
          "end": "2027-07-08"
        }
      }
    }
  },
  "meta": {
    "systems": [
      "vimshottari",
      "yogini",
      "chara"
    ],
    "date": "2026-11-20",
    "year_rule": "1 year = 12 months; fractional month = 30-day units"
  }
}

POST /v1/timezone

The correct tz for any birth: the UTC offset that was actually in force at that place on that date and time. Pass the result as tz to every other endpoint. It handles summer time (USA, UK, Europe, Australia …), half-hour and 45-minute zones (India, Nepal), India’s war time of 1941–45 (+6:30), and local mean time for births before standard time existed. Guessing tz from longitude can be wrong by an hour or more, which moves the Lagna by about 15°. Open on all plans.

POST https://kundli.soulmapbysahil.in/v1/timezone

Request Parameters

FieldTypeRequiredDescription
lat / lonfloatRequiredBirth place in decimal degrees
countrystringOptional2-letter ISO country code (IN, US, GB). Strongly recommended. Without it the zone is chosen by distance alone, which can be wrong near borders: Amritsar would get Kabul’s zone.
regionstringOptionalState or province, as an ISO 3166-2 code (US-TX) or a name (Texas). Needed for the USA, Canada and Australia, which have several zones. OpenStreetMap search returns it as ISO3166-2-lvl4.
datestringRequiredLocal date of birth: YYYY-MM-DD
timestringOptionalLocal time of birth: HH:MM (default 12:00). Matters on summer-time change days.

Request Example

POST /v1/timezone: a Delhi birth in June 1943
{
  "api_key": "your_api_key",
  "lat":     28.6139,
  "lon":     77.209,
  "country": "IN",
  "date":    "1943-06-15",
  "time":    "10:00"
}

Response

200 OK
{
  "status": "success",
  "data": {
    "tz":           6.5,
    "zone":         "Asia/Kolkata",
    "basis":        "war_time",
    "dst":          true,
    "abbreviation": "+0630",
    "note":         "India war time (+6:30) was in force on this date; clocks were 1 hour ahead of IST.",
    "zone_from":    "country",
    "warnings":     []
  }
}
  • basis is standard, daylight_saving, war_time or local_mean_time
  • zone_from says how the zone was chosen: country (one zone in that country), nearest_in_country (several zones; the nearest was used) or nearest_worldwide (no country given)
  • Source: the IANA time zone database, kept up to date on our server

MCP Server

Use the API directly inside Claude, ChatGPT, Claude Code, Cursor and any other MCP client. The AI calls our tools and reads exact calculations, so it never guesses planet positions. Ask “find Mohali and give me the reading pack for 8 July 1987, 7:25 pm” and it does the rest. Every tool call counts against your plan like a normal API call.

MCP https://kundli.soulmapbysahil.in/mcp/YOUR_API_KEY

Connect

  • Claude (claude.ai and the apps): Settings → Connectors → Add custom connector → paste https://kundli.soulmapbysahil.in/mcp/YOUR_API_KEY
  • ChatGPT: add a custom connector (developer mode) with the same URL
  • Claude Code, Cursor and other clients: use https://kundli.soulmapbysahil.in/mcp with an Authorization: Bearer header, or the URL with the key
Claude Code
claude mcp add --transport http soulos-kundli https://kundli.soulmapbysahil.in/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"
Cursor / mcp.json
{
  "mcpServers": {
    "soulos-kundli": {
      "url": "https://kundli.soulmapbysahil.in/mcp/YOUR_API_KEY"
    }
  }
}
The connector URL contains your key: treat it like a password. Create a separate key for connectors in the developer portal, so you can revoke it on its own.

Tools

ToolWhat it returns
find_placeSearch a birth city: returns lat, lon and country code
get_reading_packEverything for a reading in one call: chart, D9/D10, running Vimshottari/Yogini/Chara dashas, Jaimini karakas and arudhas, doshas
get_birth_chartLagna, 9 grahas with nakshatra/pada/house, yogas, running dasha
get_divisional_chartsAny of the 24 D-charts with degrees and reliability
get_dashasVimshottari, Yogini, Chara: running periods or full timelines
get_jaiminiKarakas, Karakamsha, Arudhas, Drishti, Argala, Chara Dasha
get_doshasMangal, Shrapit, Pitra, Sadhe Sati
match_kundliAshtakoot 36-guna matching
get_synastryGraha-Sthiti overlay of two charts
get_panchangPanchang for a date and place
get_numerologyAnkashastra
get_timezoneCorrect UTC offset for a birth moment

Pass the birth place’s country (from find_place) and the server works out the correct historical timezone itself. Responses are compact, sized for an AI’s context.


POST /v1/dosha

Detect the four classical Vedic doshas for a natal chart. All detections are Parashari BPHS only. No invented doshas, no KP, no Western equivalents. Kaal Sarpa Dosha is not included as it has no source in any classical text.

Doshas detected: Mangal Dosha (BPHS Ch. 18), Shrapit Dosha (BPHS Ch. 84), Pitra Dosha (BPHS Ch. 32), Sadhe Sati (BPHS Ch. 45).

Request

FieldTypeRequiredDescription
dobstringYesDate of birth: YYYY-MM-DD
tobstringYesTime of birth: HH:MM or HH:MM:SS (local time)
latnumberYesLatitude of birth place (decimal degrees)
lonnumberYesLongitude of birth place (decimal degrees)
tznumberNoUTC offset in hours. Default: 5.5 (IST)
gochar_datestringNoYYYY-MM-DD date for Sadhe Sati calculation (Saturn's current position). Defaults to today IST.

Example Request

POST /v1/dosha
{
  "dob":         "1990-07-15",
  "tob":         "08:30",
  "lat":         28.6139,
  "lon":         77.2090,
  "tz":          5.5,
  "gochar_date": "2026-05-24"
}

Response: data object

Response
{
  "doshas": {
    "mangal_dosha": {
      "name":                   "Mangal Dosha",
      "present":                true,
      "raw_present":            true,
      "cancelled":              false,
      "cancellation_reason":    "",
      "intensity":              "medium",
      "mars_sign":              "Aries",
      "mars_house_from_lagna":  12,
      "mars_house_from_moon":   8,
      "mars_house_from_venus":  3,
      "active_references":      [
        { "reference": "Lagna", "mars_house": 12 },
        { "reference": "Moon",  "mars_house": 8  }
      ],
      "jupiter_aspects_mars":   false,
      "source":                 "BPHS Ch. 18"
    },
    "shrapit_dosha": {
      "name":         "Shrapit Dosha",
      "present":      false,
      "saturn_sign":  "Capricorn",
      "saturn_house": 10,
      "rahu_sign":    "Gemini",
      "rahu_house":   5,
      "source":       "BPHS Ch. 84"
    },
    "pitra_dosha": {
      "name":            "Pitra Dosha",
      "present":         true,
      "triggers":        [
        { "type": "A", "description": "Rahu in 9th house from Lagna." }
      ],
      "trigger_count":  1,
      "ninth_lord":     "Mercury",
      "rahu_house":     9,
      "source":         "BPHS Ch. 32"
    },
    "sadhe_sati": {
      "name":                     "Sadhe Sati",
      "present":                  true,
      "phase":                    "peak",
      "phase_description":        "Peak phase: Saturn transiting natal Moon sign directly...",
      "natal_moon":               "Pisces",
      "gochar_saturn":             "Pisces",
      "saturn_house_from_moon":   1,
      "source":                   "BPHS Ch. 45"
    }
  },
  "natal_moon":    "Pisces",
  "lagna":         "Taurus",
  "gochar_date":   "2026-05-24",
  "gochar_saturn": "Pisces"
}

Dosha fields reference

Doshapresent = true whenCancellationsSource
Mangal Dosha Mars in houses 1, 2, 4, 7, 8, or 12 from Lagna, Moon, or Venus Mars in own sign (Aries/Scorpio) or exalted (Capricorn); Lagna is Aries/Scorpio BPHS Ch. 18
Shrapit Dosha Saturn and Rahu conjunct in the same house None: presence is the condition BPHS Ch. 84
Pitra Dosha Any of: Rahu/Ketu in 9th; Sun conjunct Rahu/Ketu in 9th; Saturn in 9th; 9th lord conjunct Saturn/Rahu/Ketu Multiple triggers increase severity (see trigger_count) BPHS Ch. 32
Sadhe Sati Gochar Saturn in 12th, 1st, or 2nd sign from natal Moon. Phase: rising / peak / setting N/A: phase ends when Saturn moves to 3rd sign from Moon BPHS Ch. 45

Notes

  • Kaal Sarpa Dosha is not included: it appears in no classical Vedic text (BPHS, Jaimini Sutras, Uttara Kalamrita, Saravali). It is a modern invention. SoulOS does not implement non-classical doshas.
  • Sadhe Sati phase lasts ~2.5 years per phase (total ~7.5 years) as Saturn transits each sign at ~30 months.
  • Mangal raw_present is true even when cancelled: useful for showing "Mangal Dosha but cancelled" text to the user.
  • Mangal jupiter_aspects_mars is provided as additional context even when it doesn't trigger cancellation.
  • All calculations use Lahiri Ayanamsa, Whole Sign houses, SoulOS Engine.

POST /v1/compatibility

Ashtakoot (8-guna) Kundali Milan compatibility score. Returns a 36-point score with all 8 gunas broken down, doshas identified, and an overall verdict.

Supports two modes:

  • Mode A: Pass boy_nakshatra, boy_rashi, girl_nakshatra, girl_rashi directly. Fast: no birth-chart calculation needed.
  • Mode B: Pass full birth details boy{} and girl{} (dob, tob, lat, lon, tz). Calculates Nakshatra and Rashi via the SoulOS Engine, then runs Ashtakoot.
POST https://kundli.soulmapbysahil.in/v1/compatibility

JSON Mode A: Direct Nakshatra/Rashi

{
  "api_key":          "your_api_key",
  "boy_nakshatra":    "Rohini",
  "boy_rashi":        "Taurus",
  "girl_nakshatra":   "Ashwini",
  "girl_rashi":       "Aries"
}

JSON Mode B: Full Birth Details

{
  "api_key": "your_api_key",
  "boy":  {
    "dob": "1994-03-15", "tob": "10:30",
    "lat": 28.6139,    "lon": 77.2090,  "tz": 5.5
  },
  "girl": {
    "dob": "1997-11-22", "tob": "14:15",
    "lat": 19.0760,    "lon": 72.8777,  "tz": 5.5
  }
}

JSON Response

{
  "status":  "success",
  "data": {
    "compatibility": {
      "total":   24.5,
      "max":     36,
      "percent": 68,
      "verdict": "Good",
      "gunas": [
        { "name": "Varna",        "max": 1,  "score": 1,   "detail": "Kshatriya · Vaishya" },
        { "name": "Vashya",       "max": 2,  "score": 2,   "detail": "Chatushpad · Chatushpad" },
        { "name": "Tara",         "max": 3,  "score": 1.5, "detail": "Sampat (Girl→Boy) · Vipat (Boy→Girl)" },
        { "name": "Yoni",         "max": 4,  "score": 3,   "detail": "Snake (Boy) · Deer (Girl)" },
        { "name": "Graha Maitri", "max": 5,  "score": 4,   "detail": "Venus→Moon: Friend · Moon→Venus: Neutral" },
        { "name": "Gana",         "max": 6,  "score": 6,   "detail": "Manav (Boy) · Manav (Girl)" },
        { "name": "Bhakoot",      "max": 7,  "score": 7,   "detail": "Taurus (Boy) · Aries (Girl)" },
        { "name": "Nadi",         "max": 8,  "score": 0,   "detail": "Aadi (Boy) · Aadi (Girl): Nadi Dosha" }
      ],
      "doshas": [
        { "type": "Nadi Dosha", "severity": "High", "description": "Same Nadi..." }
      ]
    },
    "input": {
      "boy":  { "nakshatra": "Rohini",  "rashi": "Taurus" },
      "girl": { "nakshatra": "Ashwini", "rashi": "Aries"  }
    }
  }
}

Gunas Reference

Guna Max Measures
Varna 1 Spiritual compatibility (Brahmin > Kshatriya > Vaishya > Shudra based on Rashi)
Vashya 2 Control and dominance between the two (Chatushpad, Manav, Keeta, Jaldchar)
Tara 3 Birth star harmony: auspiciousness of nakshatra positions
Yoni 4 Sexual and intimate compatibility based on nakshatra animal symbols
Graha Maitri 5 Natural friendship between the lords of the Moon signs
Gana 6 Temperament: Deva (divine), Manav (human), Rakshasa (demonical)
Bhakoot 7 Emotional and financial compatibility based on relative Moon signs
Nadi 8 Health and genetic compatibility: most critical (Dosha if same Nadi)

POST /v1/synastry

Parashari Graha-Sthiti (Planetary Overlay): places Person 1's planets into Person 2's houses and vice versa. Returns both overlays with interpretation texts, a theme summary, and a Mahadasha-level timing narrative for each person.

POST https://kundli.soulmapbysahil.in/v1/synastry

Request Parameters

FieldTypeRequiredDescription
api_keystringYesYour API key
p1objectYesPerson 1 birth details (see sub-fields below)
p2objectYesPerson 2 birth details (same structure as p1)
p1.dobstringYesDate of birth: YYYY-MM-DD
p1.tobstringYesTime of birth: HH:MM (24h)
p1.latfloatYesLatitude of birth place (decimal degrees)
p1.lonfloatYesLongitude of birth place (decimal degrees)
p1.tzfloatNoUTC offset (default 5.5 for IST)
p1.namestringNoDisplay name used in interpretation texts
interpretboolNoInclude interpretations, themes, summary, dasha narrative (default true). Pass false for raw overlay data only.

Request Example

POST /v1/synastry
{
  "api_key":   "your_api_key",
  "interpret": true,
  "p1": {
    "dob":  "1990-06-15",
    "tob":  "08:30",
    "lat":  28.6139,
    "lon":  77.2090,
    "tz":   5.5,
    "name": "Arjun"
  },
  "p2": {
    "dob":  "1993-02-20",
    "tob":  "14:15",
    "lat":  19.0760,
    "lon":  72.8777,
    "tz":   5.5,
    "name": "Priya"
  }
}

Response Structure

200 OK: Synastry Response
{
  "status": "success",
  "data": {
    "p1":        /* chart summary: lagna, 9 planets, current_dasha, nakshatra, rashi */
    "p2":        /* chart summary (same structure) */
    "p1_on_p2": /* array: P1's planets in P2's houses */ [
      {
        "planet":     "sun",
        "sign":       "Gemini",
        "sign_num":   3,
        "degree":     24.53,
        "house":      5,   // P1's Sun falls in P2's 5th house
        "retrograde": false,
        "combust":    false,
        "text":       "Arjun's Sun in Priya's 5th house...",
        "theme":      "emotional_bond",
        "intensity":  "high"
      }
      /* ... 8 more planets */
    ],
    "p2_on_p1": /* same structure: P2's planets in P1's houses */
    "themes": {              // when interpret:true
      "emotional_bond": {
        "strength":   "strong",   // strong | present | subtle
        "count":      4,
        "placements": [ /* planet, house, intensity, direction */ ]
      }
      /* themes: emotional_bond | karmic_ties | growth_friction | long_term | identity | communication */
    },
    "summary": "Arjun and Priya share a deeply karmic connection...",
    "dasha_synastry": [     // timing narrative for each person's current Mahadasha
      {
        "person":            "p1",
        "mahadasha_planet":  "saturn",
        "mahadasha_ends":    "2031-03-14",
        "antardasha_planet": "mercury",
        "antardasha_ends":   "2027-09-01",
        "house_in_partner":  7,   // P1's Saturn in P2's 7th house
        "house_in_self":     10,  // P1's Saturn in P1's own 10th house
        "narrative":         "Arjun is in their Saturn Mahadasha: a long, karmic period...",
        "natal_context":     "Arjun's Saturn in their own 10th house: the career is being tested...",
        "antardasha_focus":  "Right now the Mercury Antardasha is focusing that energy into Priya's 7th house..."
      }
      /* ... block for p2 */
    ]
  },
  "meta": {
    "response_time_ms": 412,
    "interpreted":      true,
    "ayanamsa":         "Lahiri Ayanamsa",
    "engine":           "SoulOS Engine v1.0",
    "method":           "Parashari Graha-Sthiti (Planetary Overlay)"
  }
}

Themes Reference

ThemeWhat It Measures
emotional_bond Emotional depth and intimate resonance between the two charts
karmic_ties Past-life patterns, soul-level connections, fated quality
growth_friction Challenge and growth: planets that push, stretch, and activate
long_term Structural longevity: Saturn, Jupiter placements that build over time
identity Influence on each other's sense of self (1st house, Sun, Lagna)
communication Mental connection, words, ideas, and shared understanding

Notes

  • All planetary positions use Lahiri Ayanamsa (sidereal, Parashari system)
  • House formula: ((planet_sign_A − lagna_sign_B + 12) % 12) + 1
  • Pass "interpret": false to skip texts, themes, summary, and dasha_synastry. Returns raw overlay only (faster)
  • dasha_synastry text uses real names: pass name in p1/p2 for personalised output
  • You can pass the full response to an AI API for deeper narrative generation. The structured data is designed for this

POST /v1/panchang

Daily Panchang (Hindu almanac) for any date, time, and location. Returns all 5 elements: Vara, Tithi, Nakshatra, Yoga, Karana: calculated with Lahiri Ayanamsa via the SoulOS Engine. Each element includes degree progress, degree remaining, and quality/nature rating.

Try Live Panchang + Transit Chart →

POST https://kundli.soulmapbysahil.in/v1/panchang

JSON Request Body

{
  "api_key": "your_api_key",
  "date":    "2026-05-04",   // required, YYYY-MM-DD
  "time":    "06:00",       // optional, HH:MM, defaults to "00:00"
  "lat":     28.6139,       // required
  "lon":     77.2090,       // required
  "tz":      5.5            // optional, UTC offset, defaults to 5.5
}

JSON Response

{
  "status": "success",
  "data": {
    "date":  "2026-05-04",
    "time":  "06:00",
    "vara": {
      "day":   "Monday",
      "name":  "Somavara",
      "lord":  "Moon"
    },
    "tithi": {
      "number":        7,
      "name":          "Saptami",
      "paksha":        "Shukla",
      "display":       "Shukla 7",
      "nature":        "Bhadra",
      "deg_elapsed":   8.4271,
      "deg_remaining": 3.5729
    },
    "nakshatra": {
      "index":         4,
      "name":          "Rohini",
      "lord":          "Moon",
      "pada":          2,
      "deg_elapsed":   5.1028,
      "deg_remaining": 8.2305
    },
    "yoga": {
      "number":        14,
      "name":          "Harshana",
      "quality":       "Good",
      "deg_elapsed":   4.2109,
      "deg_remaining": 9.1224
    },
    "karana": {
      "number":        14,
      "name":          "Balava",
      "quality":       "Good",
      "deg_elapsed":   2.4271,
      "deg_remaining": 3.5729
    },
    "paksha": "Shukla Paksha (Waxing)",
    "sun":    { "longitude": 19.4122,  "sign": "Aries"  },
    "moon":   { "longitude": 103.5141, "sign": "Cancer" },
    "festivals": [
      {
        "key":         "hanuman_jayanti",
        "name":        "Hanuman Jayanti",
        "name_hi":     "हनुमान जयंती",
        "description": "Birthday of Lord Hanuman: Chaitra Purnima.",
        "importance":  1,
        "region":      "all",
        "type":        "tithi",
        "fast":        true,
        "fast_type":   "phalahar",  // nirjala | phalahar | saatvik | moonrise | vigil | null
        "observance":  "sunrise"    // sunrise | noon | pradosh | nishita | moonrise | sunset | all_day
      }
    ]
  },
  "meta": { "powered_by": "SoulOS Kundli API: soulmapbysahil.in", "by": "Dr. Kohli | Kohli Media LLP", "engine": "SoulOS Engine v1.0", "ayanamsa": "Lahiri", "response_time_ms": 42 }
}

Panchang Elements Reference

Element Count Basis
Vara 7 Weekday (Sun–Sat). Each day ruled by a planet. Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn.
Tithi 30 Lunar day. Moon-Sun angle ÷ 12°. 15 Shukla (waxing) + 15 Krishna (waning).
Nakshatra 27 Moon's nakshatra. Moon longitude ÷ 13.33°. Determines the day's star quality.
Yoga 27 (Sun + Moon longitude) ÷ 13.33°. Each yoga has an auspiciousness rating.
Karana 11 Half-tithi. 7 movable karanas cycle 8 times + 4 fixed karanas. 6° per karana.

Festivals Array: Field Reference

Each object in the festivals array contains the following fields. Array is sorted by importance ascending (most important first). Empty array if no festival today.

Field Type Description
key string Unique identifier for the festival (e.g. "diwali", "maha_shivaratri").
name string English name of the festival.
name_hi string Hindi name (Unicode). May be empty for minor observances.
description string Short description: what is observed and why.
importance int (1–3) 1 = major national festival, 2 = significant regional, 3 = minor / monthly.
region string "all" or a regional identifier (e.g. "north", "south", "maharashtra", "gujarat").
type string Basis for date calculation: tithi | nakshatra | sankranti | combined.
fast bool Whether a fast (vrat) is traditionally observed on this day.
fast_type string|null Type of fast: nirjala (waterless), phalahar (fruits only), saatvik (no grains), moonrise (break at moonrise), vigil (all-night fast), or null if not a fasting day.
observance string When the primary ritual or puja is performed: sunrise | noon | pradosh | nishita | moonrise | sunset | all_day.

POST /v1/ankashastra

Vedic Ankashastra: the classical planetary number system. Sun=1 Moon=2 Jupiter=3 Rahu=4 Mercury=5 Venus=6 Ketu=7 Saturn=8 Mars=9.

Computes Moolank (birth number), Bhagyank (destiny number), Universal Day, Personal Day, and optionally Naam Ank (name number). All numbers reduce to 1–9. No master numbers. Compatibility uses Naisargik Maitri from BPHS.

This is the only correct Vedic numerology. Not Pythagorean (A=1,B=2…). Not Chaldean. The letter mapping is phonetic. Based on each sound's planetary resonance per classical Vedic tradition.

Request

FieldTypeRequiredDescription
dobstringYesDate of birth: YYYY-MM-DD
namestringNoFull name: triggers Naam Ank calculation and Moolank–name compatibility
datestringNoYYYY-MM-DD: date for Universal Day and Personal Day. Defaults to today IST.
moon_rashiintegerNoNatal Moon sign 1–12 (Aries=1 … Pisces=12). Enables Moolank ↔ Moon-lord compatibility block.

Example Request: Moolank + Bhagyank only

POST /v1/ankashastra
{
  "dob":         "1990-07-15",
  "date":        "2026-05-25"
}

Example Request: with name and Moon sign

POST /v1/ankashastra
{
  "dob":         "1990-07-15",
  "name":        "Sahil",
  "date":        "2026-05-25",
  "moon_rashi":  8
}

Response: data object

Response
{
  "moolank": {
    "number":        6,
    "planet":        "Venus",
    "planet_hi":     "शुक्र",
    "planet_hg":     "Venus (Shukra)",
    "sanskrit":      "Shukra",
    "qualities_en":  "Love, beauty, harmony, creativity, relationships",
    "qualities_hi":  "प्रेम, सौंदर्य, सामंजस्य, रचनात्मकता",
    "qualities_hg":  "Love, beauty, harmony, creativity",
    "nature_en":     "Venus blesses with charm, artistic sense, and a deep need for beauty...",
    "nature_hi":     "शुक्र को सौंदर्य, कला और सहचर्य का आशीर्वाद देता है...",
    "nature_hg":     "Venus deta hai charm, artistic sense...",
    "lucky_day_en":  "Friday",
    "lucky_day_hi":  "शुक्रवार",
    "lucky_color_en": "White, Cream, Pale Pink",
    "lucky_gem_en":   "Diamond (Heera)",
    "birth_days":    [6, 15, 24],
    "deity":         "Lakshmi"
  },
  "bhagyank": {
    "number":  4,
    "planet":  "Rahu"
    // ...same fields as moolank...
  },
  "universal_day": {
    "number":  3,
    "planet":  "Jupiter",
    "date":    "2026-05-25"
    // ...same fields as moolank...
  },
  "personal_day": {
    "number":  9,
    "planet":  "Mars",
    "date":    "2026-05-25"
    // ...same fields as moolank...
  },
  "naam_ank": {
    "number":       4,
    "planet":       "Rahu",
    "name_used":    "SAHIL",
    "raw_sum":      13,
    "letter_map":   { "S":3, "A":1, "H":5, "I":1, "L":3 },
    "moolank_compatibility": {
      "code":      "F",
      "en":        "Friend",
      "hi":        "मित्र",
      "hg":        "Mitra (Friend)",
      "effect_en": "Supportive and harmonious. Natural alignment of energies.",
      "planets":   ["Venus", "Rahu"]
    }
    // ...same planet fields as moolank...
  },
  "compatibility": {
    "moolank_bhagyank": {
      "code":      "N",
      "en":        "Neutral",
      "hi":        "सम",
      "effect_en": "Mixed results. Neither blocked nor fully supported.",
      "planets":   ["Venus", "Rahu"]
    },
    "moolank_moon_lord": {
      "code":       "E",
      "en":         "Enemy",
      "effect_en":  "Friction and challenge. Growth comes through conscious effort.",
      "moon_rashi": "Scorpio",
      "moon_lord":  "Mars",
      "planets":    ["Venus", "Mars"]
    }
  }
}

Planetary Number System

NumberPlanetSanskritBirth DaysQualities
1Sun (Surya)सूर्य1, 10, 19, 28Leadership, authority, clarity of purpose
2Moon (Chandra)चंद्र2, 11, 20, 29Intuition, sensitivity, nurturing
3Jupiter (Guru)गुरु3, 12, 21, 30Wisdom, expansion, dharma, generosity
4Rahuराहु4, 13, 22, 31Ambition, transformation, unconventional paths
5Mercury (Budha)बुध5, 14, 23Intelligence, communication, adaptability
6Venus (Shukra)शुक्र6, 15, 24Love, beauty, harmony, creativity
7Ketuकेतु7, 16, 25Spirituality, intuition, liberation, detachment
8Saturn (Shani)शनि8, 17, 26Discipline, karma, structure, endurance
9Mars (Mangal)मंगल9, 18, 27Energy, courage, action, completion

Vedic Letter Mapping (Naam Ank)

Based on Sanskrit phonetic affinity: NOT Pythagorean sequential (A=1,B=2…). Each letter group shares sound-energy with its ruling planet.

NumberPlanetLetters
1SunA, I, J, Q, Y
2MoonB, K, R
3JupiterC, G, L, S
4RahuD, M, T
5MercuryE, H, N, X
6VenusU, V, W
7KetuO, Z
8SaturnF, P
9MarsAll remaining letters

Compatibility Codes (Naisargik Maitri)

CodeMeaningEffect
FFriend (Mitra)Supportive and harmonious. Natural alignment of energies.
NNeutral (Sama)Mixed results. Neither blocked nor fully supported.
EEnemy (Shatru)Friction and challenge. Growth comes through conscious effort.

Notes

  • No master numbers. 11 reduces to 2, 22 reduces to 4. Always 1–9 per Vedic Ankashastra.
  • Moolank = birth day digits only. Born 17th: 1+7=8 (Saturn).
  • Bhagyank = full DOB all digits. 15/08/1990: 1+5+0+8+1+9+9+0=33 → 3+3=6 (Venus).
  • Universal Day = today's date digits reduced. Same for everyone on that date.
  • Personal Day = reduce(Moolank + Universal Day). Unique per person, changes daily.
  • Naam Ank strips non-alphabetic characters, uppercases the string, maps each letter via the Vedic phonetic table, sums all values, and reduces to 1–9.
  • Compatibility is drawn from BPHS Naisargik Maitri (natural friendship between planet lords).
  • This endpoint requires only DOB: no time, place, or coordinates needed.

Support

For integration help, partnership, or enterprise access. Reach out directly. We respond fast.

care@kohli.tel soulmapbysahil.in Get Free Key

Frequently Asked Questions

Quick answers for developers integrating the SoulOS Kundli API.

What is the API endpoint? +

POST https://kundli.soulmapbysahil.in/v1/chart, send JSON with dob (YYYY-MM-DD), tob (HH:MM), lat (decimal), lon (decimal), tz (float, default 5.5), and your api_key or Authorization: Bearer header.

How many Dasha levels are returned? +

All 5 levels, Mahadasha, Antardasha, Pratyantar, Sookshma, and Prana, with exact start and end dates. Use dasha_depth (1–5) to limit depth. dasha_depth=1 gives 9 MD entries; dasha_depth=5 gives all ~66,000 entries pre-calculated.

Which ayanamsa and house system? +

Lahiri ayanamsa (Chitra Paksha, official Indian government standard) and Whole Sign houses as prescribed by Maharishi Parashar in BPHS. The ayanamsa value is returned in every response under meta.ayanamsa.

What yogas does the API detect? +

40 Parashari Yogas across 7 categories: Pancha Mahapurusha, Raja, Dhana, Chandra, Surya, Viparita Raja, and Special. Each yoga includes name, category, nature (benefic/challenging), description, planets involved, and house positions. Only actually-present yogas are returned. Empty array if none.

Is there a free tier? +

Yes. 100 calls/day forever free: no credit card required. Register at /dev/register.php. Paid plans start at ₹499/month for 1,000 calls/day.

What does the response include? +

basic (lagna, rashi, nakshatra), planets (9 planets with sign, degree, nakshatra, pada, retrograde, combust), houses (12), nakshatras, avkahada chakra, dasha (5-level Vimshottari + current chain), yogas, lagna_degree, combustion map.

How does the Kundali Milan / compatibility API work? +

POST /v1/compatibility: Mode A: pass boy_nakshatra, boy_rashi, girl_nakshatra, girl_rashi directly. Mode B: pass full boy{} and girl{} birth details (dob, tob, lat, lon, tz) and the API calculates Nakshatra/Rashi from the birth details. Returns all 8 Ashtakoot gunas (Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi), total score out of 36, percentage, verdict, and any doshas present.

How does the Panchang API work? +

POST /v1/panchang with date (YYYY-MM-DD), time (HH:MM, optional), lat, lon, and tz. Returns all 5 Panchang elements. Vara (weekday + lord), Tithi (lunar day + paksha + nature), Nakshatra (Moon star + pada + lord), Yoga (Sun+Moon combination + quality), and Karana (half-tithi + quality): with degree elapsed/remaining for each element so you can show progress within the current element.

What is POST /v1/synastry and how is it different from compatibility? +

POST /v1/synastry implements Parashari Graha-Sthiti: a planetary overlay technique. It places Person 1's planets into Person 2's houses and vice versa to show how each person's planetary energy lands in specific life domains of their partner. Unlike Ashtakoot compatibility (which scores by Nakshatra), synastry works at the degree level with the full birth chart. It returns both overlays (p1_on_p2 and p2_on_p1), 108 interpretation texts, a themes summary, and a Mahadasha-level timing narrative showing which life chapter each person is currently running and where that energy lands in the partner's chart.

Which divisional charts does the API support? +

POST /v1/divisional returns 24 charts: all 16 Shodashavarga charts (D1 to D60), plus D5, D6, D8, D11, D81, D108, D144 and D150. Every chart includes the Lagna degree and each planet degree, and a birth-time window showing how many minutes the birth time can be off before that chart Lagna changes sign. All 24 are available on every plan, including Free.

Does the API support the Jaimini system? +

Yes. POST /v1/jaimini returns Chara Karakas (8 or 7 scheme), Karakamsha with Ishta Devata, Arudha Padas A1 to A12 including Arudha Lagna and Upapada, Rashi Drishti, Argala, and Chara Dasha (K.N. Rao method) with antardashas and the running period. Use include to pick sections. Open on all plans.

Which dasha systems does the API calculate? +

POST /v1/dasha returns Vimshottari (up to 5 levels, Mahadasha to Prana), Yogini (36-year cycle) and Jaimini Chara Dasha in one call, each with the balance at birth, the periods running on any date and the full timeline. Pass timeline=false for a small response with only what is running now.

How accurate is the SoulOS Kundli API? +

It was checked against the published charts of Mahatma Gandhi, Jawaharlal Nehru, Indira Gandhi, Swami Vivekananda and Sachin Tendulkar: Lagna and all planets agree within about 1 arc-minute, every D1 and D9 sign is identical and the Vimshottari balance at birth matches. SoulOS Engine with Lahiri ayanamsa.

Why use a Kundli API instead of building the calculations myself? +

Planet positions are easy with an ephemeris library. The hard part is the Jyotish layer: 24 divisional chart rules, Jaimini school choices, dasha edge cases (the birth Mahadasha must start before birth), birth-time sensitivity and verification against known charts. This API does all of that, is checked against published charts, and costs from free to ₹499/month.

How does it compare with other astrology APIs? +

It is the lowest-priced paid plan we found (₹499 for 1,000 calls/day), gives every feature on the free plan, and offers 24 divisional charts with degrees and birth-time reliability, Jaimini and three dasha systems. Other providers currently offer things we do not, such as KP, PDF reports, Western astrology and MCP servers. See the comparison table in the docs.