What is the Vedic Kundli PDF API?

It is a single endpoint, POST /api/v3/pdf/vedic-kundli-report, that takes birth data and returns a finished 35-43 page Jyotish kundli as a PDF. The report has 19 sections, every one interpreted in plain language, and renders in 9 languages including native Hindi, Tamil, and Telugu. You send one request with your chosen ayanamsa, chart style, and node type, and get back a report you can sell as is.

How many pages is the report and how many sections?

The PDF runs 35 to 43 pages depending on the chart, and it has 19 sections. Those sections cover the Panchanga, the D1 chart, a planetary table, Nakshatra, Lagna, the D9 Navamsa, Yogas, Doshas, Vimshottari and Yogini dashas, Ashtakavarga, Shadbala, the D10 career chart, Jaimini soul readings, Pushkara, Gochara transits, the D60, remedies, and a glossary. None of them are data-only pages.

Which languages does the report support?

Nine: English, Hindi, Tamil, Telugu, Russian, German, French, Spanish, and Portuguese. Set pdf_options.language to en, hi, ta, te, ru, de, fr, es, or pt. For Hindi, Tamil, and Telugu the report uses real Devanagari, Tamil, and Telugu script with native astrological terminology, not romanized transliteration.

Are the Hindi, Tamil, and Telugu reports real script?

Yes. They use embedded Noto Devanagari, Tamil, and Telugu fonts inside the PDF, so the script renders correctly on any device with no missing-character boxes. The astrological terms are written the native way a Jyotish reader expects, not English words spelled out in Latin letters. This is the part most multilingual claims fall down on, and it is handled here.

What does a request look like?

Send a JSON body with a subject (name and birth_data: year, month, day, hour, minute, city, country_code), plus ayanamsa, chart_style, node_type, karaka_scheme, tradition, and pdf_options with the language. For example, ayanamsa lahiri, chart_style north_indian, node_type mean, karaka_scheme 8, language en. The endpoint returns application/pdf.

Which ayanamsa options are available?

Four. lahiri is the default and the Indian Government standard, raman follows B.V. Raman's value, kp is the Krishnamurti Paddhati ayanamsa, and true_citra fixes Spica. You pick one per request, so a single integration can serve KP users and Lahiri users without separate code.

Which chart styles can I render?

Three: north_indian, the diamond layout used across North India; south_indian, the fixed square grid; and east_indian, the Bengali style. Set chart_style in the request and the D1, Navamsa, and other charts draw in that style throughout the report.

What is the new Jaimini endpoint?

POST /api/v3/vedic/jaimini is a companion endpoint that returns the Jaimini soul indicators on their own: the chara karakas including Atmakaraka and Darakaraka, plus Karakamsa and Arudha. It uses the 8-karaka scheme with Rahu by default and a 1-arcminute tie-guard so karaka assignment stays stable. Use it to build soul-indicator features without generating a full PDF each time.

What is the Atmakaraka and Darakaraka?

Among the chara karakas, the Atmakaraka is the soul significator, the planet sitting at the highest degree in the chart, and the Darakaraka is the spouse significator, the planet at the lowest degree. The Jaimini endpoint and the PDF both compute them. They drive soul-purpose and relationship readings that consumer kundli apps usually cannot offer.

How are Yogas handled?

Yogas are checked for Bhanga, the cancellation conditions, before the report states a verdict. A yoga that is technically present but cancelled is not presented to the user as active. This avoids the common false positive where an app proudly announces a Raja Yoga that classical rules actually cancel.

What divisional charts are in the report?

The D1 rashi chart, the D9 Navamsa shown two-up against the rashi, the D10 Dasamsa for career, and the D60 Shashtiamsa. The D60 is birth-time-gated: when the birth time is too uncertain for a reliable D60, the report says so rather than guessing the deity and nature.

What visuals are in the PDF?

The D1 chart in your chosen style, the Navamsa shown two-up, an Ashtakavarga bar chart, and a Vimshottari dasha timeline. The visuals are rendered into the PDF, so you get charts and graphics without building any drawing code on your side.

Do I need more than one API call?

No. One POST to the PDF endpoint returns the whole 35-43 page report. You do not chain calls or stitch sections together, and you do not write your own PDF layout. If you also want the Jaimini soul indicators as data, that is a second optional endpoint, but the report itself is one call.

What birth data does the endpoint need?

A subject with a name and birth_data: year, month, day, hour, minute, plus a city and country_code (or latitude, longitude, and timezone). The API resolves the location and builds the sidereal chart before rendering the report. Birth time matters, especially for the time-gated D60 section.

Can I switch between mean and true nodes?

Yes. node_type takes mean or true, controlling whether Rahu and Ketu are computed as the mean lunar node or the true (osculating) node. Some schools prefer one over the other, so it is a request field rather than a fixed choice baked into the API.

What is the karaka_scheme option?

It sets how many chara karakas the Jaimini calculation uses: 7 or 8. The 8-karaka scheme, which includes Rahu, is the default. The 1-arcminute tie-guard keeps the assignment stable when two planets sit at nearly the same degree, which would otherwise flip the Atmakaraka unpredictably.

How much does the Vedic Kundli PDF API cost?

The Always Free tier includes 50 requests per month. Starter is $11/month, Professional is $37/month for 55,000 requests, Business is $99/month for 220,000 requests, and Enterprise is $399+/month with unlimited usage and dedicated servers. Each report is one request.

Is there a free tier?

Yes. Every account gets 50 free requests per month with no card required, so you can generate real kundli PDFs in every language and check the Hindi, Tamil, and Telugu rendering against your own reference charts before you commit to a paid plan.

Jyotish app developers, indie SaaS builders, and astrologer-entrepreneurs who want to sell a premium kundli report without building a 40-page report engine and an Indic-font rendering pipeline themselves. It is built to serve the Indian and multilingual market, which is exactly where most astrology APIs fall short.

How do I integrate it into my app?

Send one POST with birth data and your options, then save or stream the returned PDF to your user. Most teams wire it to an in-app purchase or a generate-report button and are live in under an hour. For soul-indicator features, add the Jaimini endpoint. Pair it with our Vimshottari Dasha or Divisional Charts APIs for raw data alongside the report.

Vedic Kundli PDF

A Sellable Jyotish Kundli PDF From One API Call

POST to /api/v3/pdf/vedic-kundli-report and get back a 35-43 page, fully interpreted Jyotish kundli: 19 sections, rendered in 9 languages with native Hindi, Tamil, and Telugu type, not transliteration.

Pick your ayanamsa, chart style, and node type. The hard parts most APIs skip are already done.

View Demo

35-43

Pages Per Report

Interpreted Sections

Output Languages

Chart Styles

Built for Jyotish app developers and astrologer-entrepreneurs

Embedded Devanagari, Tamil, and Telugu fonts

Every section interpreted, no data-only pages

Most APIs return raw JSON, leaving you to design and write a 40-page report yourself
Hindi, Tamil, and Telugu break because the fonts and native terms are never bundled
Vimshottari dasha, Ashtakavarga, and Shadbala come as numbers with no reading attached
Yogas are flagged without checking Bhanga, so a cancelled yoga still shows as active
Doshas like Manglik or Kaal Sarpa are reported full-strength with no partial or phase detail
Jaimini soul indicators and chara karakas are simply missing from the output

Replace raw data with

One POST returns a finished 35-43 page kundli PDF, ready to email or sell as is
Real Hindi, Tamil, and Telugu with embedded Noto fonts and native astrological terms
Vimshottari and Yogini dashas, Ashtakavarga, and Shadbala each come with a written reading
Yogas are checked for Bhanga cancellation before the report states the verdict
Manglik is house-specific, Kaal Sarpa shows full versus partial, Sade Sati is phase-aware
A new Jaimini endpoint adds Atmakaraka, Darakaraka, Karakamsa, and Arudha soul indicators

Built to Ship a Premium Jyotish Report

Classical depth, one API call

35-43 pages

Report Length

Interpreted Sections

Output Languages

Ayanamsa Options

Chart Styles

API Calls Needed

What's Inside the Report

Nineteen interpreted sections from one API call

Cover and Panchanga

Opens with the five limbs of the birth day: tithi, vara, nakshatra, yoga, and karana

D1 Chart, Your Style

The rashi chart drawn north_indian, south_indian, or east_indian as you choose

Full Planetary Table

Combust orb, Baladi avastha, Panchadha-Maitri dignity, Pushkara, and Bhava-Chalit cusps

Nakshatra and Lagna

Detailed Nakshatra reading and the ascendant interpretation

D9 Navamsa Two-Up

The marriage and dharma chart shown alongside the rashi for quick comparison

Yogas, Bhanga Checked

Cancellation conditions tested before the report states whether a yoga is active

Doshas With Nuance

House-specific Manglik, full-vs-partial Kaal Sarpa with provenance, phase-aware Sade Sati

Vimshottari and Yogini

Both dasha systems with a timeline visual and written period readings

Ashtakavarga Chart

A bar chart of the bindus showing which signs carry strength

Shadbala Six-Fold

Planetary strength with Ishta and Kashta phala for benefic and malefic yield

D10 and Jaimini

The Dasamsa career chart plus Atmakaraka, Darakaraka, Karakamsa, and Arudha readings

Gochara, D60, Remedies

Transits from the Moon with bindus, the birth-time-gated D60, remedies, and a glossary

Vedic Kundli PDF API Documentation

A 19-section Jyotish report in 9 languages from a single endpoint

The Vedic Kundli PDF API turns birth data into a finished Jyotish report. One POST to /api/v3/pdf/vedic-kundli-report returns a 35-43 page PDF with 19 sections, every one of them interpreted in plain language rather than dumped as a table. The request is small: a subject with name and birth data, plus your choices for ayanamsa (lahiri, raman, kp, or true_citra), chart_style (north_indian, south_indian, or east_indian), node_type (mean or true), and the report language inside pdf_options. The output is the part most teams never finish on their own: a cover with the Panchanga, the D1 chart in your chosen style, a full planetary table, Nakshatra detail, the Lagna reading, the D9 Navamsa, Yogas checked for cancellation, Doshas with real nuance, Vimshottari and Yogini dashas, Ashtakavarga, Shadbala, the D10 career chart, Jaimini soul readings, Gochara transits, the D60, remedies, and a glossary. It renders in nine languages with native Hindi, Tamil, and Telugu type. If you are building a kundli app and the report is what is standing between you and launch, this endpoint is the report.

What does the Vedic Kundli PDF API return?

It returns a single application/pdf file, 35 to 43 pages long, with 19 sections that are each written out, not left as raw numbers.

The report opens with a cover and the Panchanga, the five limbs of the birth day.

Then comes your D1 chart in the style you picked, a planetary table with combust orb, Baladi avastha, Panchadha-Maitri dignity, Pushkara, and Bhava-Chalit cusps, followed by Nakshatra detail and the Lagna reading.

After that you get the D9 Navamsa shown two-up, Yogas with Bhanga checked, Doshas, the Vimshottari and Yogini dasha timelines, the Ashtakavarga bar chart, Shadbala six-fold strength, the D10 Dasamsa for career, Jaimini soul readings, Pushkara, Gochara transits, the D60 Shashtiamsa, remedies, and a glossary.

You send one request and get a report you could put in front of a paying user without editing a word.

One PDF, 35-43 pages, 19 interpreted sections, no data-only pages

1 min read

How does the 9-language rendering actually work?

This is the part most Vedic APIs skip, because it is the part that is genuinely hard.

Set pdf_options.language to one of en, hi, ta, te, ru, de, fr, es, or pt and the whole report renders in that language.

For Hindi, Tamil, and Telugu that means real Devanagari, Tamil, and Telugu script, with the Noto fonts embedded in the PDF so the glyphs render anywhere, on any device, with no missing-character boxes.

It also means native astrological vocabulary: the terms a Jyotish reader expects, written the way they are written in that tradition, not romanized.

Most APIs that claim multilingual support hand you English text with a few words swapped, or break entirely when a Tamil glyph appears.

Here the fonts and the terminology are bundled into the render, so a Hindi-speaking or Tamil-speaking user gets a report that reads as if it were written for them.

Native Hindi, Tamil, Telugu with embedded Noto fonts, not transliteration

1 min read

Which ayanamsa and chart styles can I choose?

Four ayanamsa options cover the schools your users follow.

lahiri is the default and the Indian Government standard, raman follows B.V.

Raman's value, kp is the Krishnamurti Paddhati ayanamsa for KP astrologers, and true_citra fixes Spica at the start of the relevant sign.

You pick one per request, so a single integration can serve KP users and Lahiri users from the same code.

For the chart drawing, chart_style takes north_indian for the diamond layout common across North India, south_indian for the fixed square grid, or east_indian for the Bengali style.

Node_type lets you choose mean or true Rahu and Ketu, and karaka_scheme switches the Jaimini chara karakas between the 7-karaka and 8-karaka counts.

Every one of these is a request field, so you expose the choice to your users without maintaining separate code paths.

4 ayanamsa, 3 chart styles, mean or true nodes, 7 or 8 karakas

1 min read

How are dashas, Ashtakavarga, and Shadbala handled?

Each timing and strength system comes with a reading, not just a grid.

The Vimshottari dasha section draws a timeline visual of the mahadasha sequence and explains the periods, and the Yogini dasha adds the eight-fold timing cycle alongside it.

Ashtakavarga is shown as a bar chart of the bindus, so a user sees at a glance which signs carry strength.

Shadbala gives the six-fold strength for every planet, and adds Ishta and Kashta phala, the benefic and malefic yields, so the strength numbers connect to a result rather than floating on their own.

The Gochara section reads canonical transits from the Moon and overlays the Ashtakavarga bindus, which is how classical transit reading actually works.

You get the picture and the words together, which is what makes the report sellable instead of a data export.

Vimshottari and Yogini dashas, Ashtakavarga bindus, Shadbala with Ishta and Kashta phala

1 min read

What does the new Jaimini endpoint add?

Alongside the PDF, there is a companion public calculation endpoint, POST /api/v3/vedic/jaimini, that returns the Jaimini soul indicators on their own.

It computes the chara karakas, the Atmakaraka (the soul significator, the planet at the highest degree) and the Darakaraka (the spouse significator, the lowest), plus the Karakamsa and the Arudha.

The default is the 8-karaka scheme that includes Rahu, and a 1-arcminute tie-guard handles the rare case where two planets sit at nearly the same degree, so the karaka assignment stays stable.

The same Jaimini readings appear inside the PDF report, but the standalone endpoint lets you build soul-indicator features, like an Atmakaraka lookup or a Darakaraka compatibility tool, without generating a full report each time.

It is a clean way to add a Jaimini layer to an existing app.

POST /api/v3/vedic/jaimini for Atmakaraka, Darakaraka, Karakamsa, Arudha

1 min read

How do Doshas and Yogas avoid false positives?

Bad dosha and yoga logic is the fastest way to lose trust, so this report does the checks a careful astrologer would.

Yogas are tested for Bhanga, the cancellation conditions, before the report states a verdict, so a yoga that is technically present but cancelled is not sold to the user as active.

Doshas carry the same nuance.

Manglik is read house by house, since the affliction differs by the house Mars sits in.

Kaal Sarpa is reported as full versus partial with its provenance, so a partial pattern is not overstated.

Sade Sati is phase-aware, telling the user which of the three phases of Saturn's transit over the Moon they are in rather than just flagging it on or off.

The D60 Shashtiamsa is birth-time-gated, so when the birth time is too uncertain for a reliable D60, the report says so instead of guessing a deity and nature.

Bhanga-checked Yogas, house-specific Manglik, full-vs-partial Kaal Sarpa, phase-aware Sade Sati

1 min read

Use Cases

Jyotish Mobile Apps

Sell a premium kundli PDF as an in-app purchase without building a report engine

Indian-Market SaaS

Serve Hindi, Tamil, and Telugu users a report in real native script, not romanized text

Astrologer-Entrepreneur Tools

Let astrologers generate a branded 40-page reading for clients in seconds

Soul-Indicator Features

Use the Jaimini endpoint for Atmakaraka and Darakaraka tools on their own

Matchmaking Platforms

Pair Darakaraka readings and Navamsa detail into compatibility products

Content and Education

Generate readable example kundlis with a glossary for teaching and articles

Technical Specifications

PDF Endpoint	POST /api/v3/pdf/vedic-kundli-report
Jaimini Endpoint	POST /api/v3/vedic/jaimini
Output Format	application/pdf
Report Length	35-43 pages
Sections	19, all interpreted
Languages	en, hi, ta, te, ru, de, fr, es, pt
Indic Fonts	Embedded Noto Devanagari, Tamil, Telugu
Ayanamsa	lahiri, raman, kp, true_citra
Chart Styles	north_indian, south_indian, east_indian
Node Type	mean or true
Karaka Scheme	7 or 8 (8 default, with Rahu)
Divisional Charts	D1, D9 Navamsa, D10 Dasamsa, D60
Dashas	Vimshottari and Yogini
Strength Systems	Ashtakavarga, Shadbala, Ishta/Kashta
Jaimini Karakas	Atmakaraka, Darakaraka, Karakamsa, Arudha
Tie Handling	1-arcminute karaka tie-guard
Doshas	Manglik, Kaal Sarpa, Sade Sati
Visuals	D1, Navamsa 2-up, Ashtakavarga chart, dasha timeline
Input Formats	City + country or lat/long + timezone
Language Field	pdf_options.language

Vedic Kundli PDF API Comparison

Feature	Astrology API	Others
Output	Finished 35-43 page PDF	Raw JSON only
Interpretation	All 19 sections written	Numbers, no reading
Languages	9, native script	English only
Indic Fonts	Embedded Noto Devanagari, Tamil, Telugu	Missing or broken glyphs
Ayanamsa Options	4 (lahiri, raman, kp, true_citra)	Lahiri only
Chart Styles	North, South, East Indian	One fixed style
Yoga Cancellation	Bhanga checked	Not checked
Dosha Nuance	Partial, phase, house-specific	On/off flag
Jaimini Karakas		×
Shadbala + Ishta/Kashta		×
Calls to Ship a Report	1	Many, plus your own PDF code
Price	$11/month	$49-99/month
Free Tier	50 requests	No free tier

Related Vedic APIs

Vedic Astrology API

Full sidereal birth chart calculations

Vedic Aspects API

Graha drishti, Drik Bala, and Jaimini aspects

Vedic Birth Chart API

Sidereal natal chart data and houses

Nakshatra API

27 nakshatras and padas

Vimshottari Dasha API

Dasha and antardasha periods

Divisional Charts API

Varga charts D1 through D60

PDF Report API

All report types in one PDF endpoint family

References & Standards

Swiss Ephemeris (DE431-based) — astronomical calculations source
NASA JPL Planetary Ephemerides — underlying ephemeris dataset
International Astronomical Union (IAU) — body designation and nomenclature standards
IANA Time Zone Database — timezone & DST resolution

Simple, Transparent Pricing

Start free, scale as you grow. No hidden fees, no surprises.

Always Free

Start Free

Perfect for learning, testing, and small personal projects

50 API calls/month

Basic natal charts

5 house systems

Community support

Pro

$11/month

For small apps and personal projects

All basic endpoints
12 house systems
Email support

Best Value

Pro Plus

$21/month

For growing apps and medium traffic

All enhanced endpoints
18 house systems
AI interpretations
Priority email support

Ultra

$37/month

For professional astrology applications

Credit math ↓

All premium endpoints
23 house systems
Advanced AI interpretations
Priority support

High Volume Plans

For enterprise-scale applications

Business

$99/month

For high-volume applications

Credit math ↓

ALL endpoints
White-label ready
Custom AI fine-tuning
Phone support

UNLIMITED

Enterprise

$399+per month

Unlimited requests with dedicated infrastructure

Dedicated server infrastructure
Sub-300ms guaranteed
24/7 dedicated support
99.99% uptime SLA

All plans include comprehensive documentation and SDKs

Questions? Talk to our team

Vedic Kundli PDF API FAQ

Jyotish reports, languages, and the Jaimini endpoint answered

Complete Your Jyotish Stack

The Vedic Kundli PDF API pairs with the rest of our sidereal toolkit. Add

vedic astrology charts vedic aspects vedic birth charts nakshatras vimshottari dasha divisional charts pdf reports

Ship a Jyotish Report Your Users

Skip the report engine and the Indic-font pipeline. Get a 35-43 page, 19-section kundli in 9 languages, with native Hindi, Tamil, and Telugu, from one POST.

Start Free Now Compare Features

30 day money back

Free integration support

No setup fees

A Sellable Jyotish Kundli PDF From One API Call

Why Jyotish Apps Are Hard to Ship

Astrology API Vedic Kundli PDF

Built to Ship a Premium Jyotish Report

What's Inside the Report

Cover and Panchanga

D1 Chart, Your Style

Full Planetary Table

Nakshatra and Lagna

D9 Navamsa Two-Up

Yogas, Bhanga Checked

Doshas With Nuance

Vimshottari and Yogini

Ashtakavarga Chart

Shadbala Six-Fold

D10 and Jaimini

Gochara, D60, Remedies

Vedic Kundli PDF API Documentation

What does the Vedic Kundli PDF API return?

How does the 9-language rendering actually work?

Which ayanamsa and chart styles can I choose?

How are dashas, Ashtakavarga, and Shadbala handled?

What does the new Jaimini endpoint add?

How do Doshas and Yogas avoid false positives?

Use Cases

Jyotish Mobile Apps

Indian-Market SaaS

Astrologer-Entrepreneur Tools

Soul-Indicator Features

Matchmaking Platforms

Content and Education

Technical Specifications

Vedic Kundli PDF API Comparison

Related Vedic APIs

Vedic Astrology API

Vedic Aspects API

Vedic Birth Chart API

Nakshatra API

Vimshottari Dasha API

Divisional Charts API

PDF Report API

References & Standards

Simple, Transparent Pricing

Always Free

Pro

Pro Plus

Ultra

High Volume Plans

Business

Enterprise

Vedic Kundli PDF API FAQ

What is the Vedic Kundli PDF API?

How many pages is the report and how many sections?

Which languages does the report support?

Are the Hindi, Tamil, and Telugu reports real script?

What does a request look like?

Which ayanamsa options are available?

Which chart styles can I render?

What is the new Jaimini endpoint?

What is the Atmakaraka and Darakaraka?

How are Yogas handled?

How detailed are the Doshas?

What dasha systems are included?

Does the report include Ashtakavarga and Shadbala?

What divisional charts are in the report?

What visuals are in the PDF?

Do I need more than one API call?

What birth data does the endpoint need?

Can I switch between mean and true nodes?

What is the karaka_scheme option?

How much does the Vedic Kundli PDF API cost?

Is there a free tier?

Who is this API for?

How do I integrate it into my app?

Complete Your Jyotish Stack

Ship a Jyotish Report Your Users

Why Jyotish Apps Are Hard to Ship

Astrology API Vedic Kundli PDF

Built to Ship a Premium Jyotish Report

What's Inside the Report