Generating white-label PDF astrology reports via API

White-label PDF astrology reports let you sell a finished, branded deliverable—a multi-page kundli, natal, or compatibility document—without building a chart engine, an interpretation library, or a PDF renderer yourself. With the Vedika API you send birth details to a report endpoint, and you get back a generated document grounded in computed placements and classical-text interpretations that you can host and distribute under your own brand. This guide walks through the request shapes, the systems you can cover, and the integration code to wire it into your product.

What a report API actually does for you

A single astrology report is deceptively expensive to produce. You need an ephemeris precise enough that the ascendant and house cusps are correct, a chart layer that derives divisional charts, dashas, yogas, and aspects, an interpretation layer that maps those placements to readable text, and a typesetting layer that lays it all out across dozens of pages. Each of those is its own multi-month project, and getting any one wrong undermines the whole document.

The report API collapses that stack into one HTTP call. You supply the birth data and the report type; the platform computes the chart, assembles the interpretation, renders the pages, and hands back a document. The pieces that are hardest to get right—astronomical precision and source-traceable interpretation—are handled server-side and are the same pieces this article focuses on.

White-label means resale-ready

"White-label" is the practical reason teams reach for this. The generated report is meant to be the product you sell: your cover, your logo, your color theme on the page, your customer reading it. There is no third-party watermark or attribution forced onto the deliverable. You decide whether it lives behind a paywall in your app, gets emailed after a consultation, or is bundled into a subscription.

The endpoints you'll use

Vedika exposes 700+ API operations across 25 domains (704 enumerated as of June 2026). For reports, you work with a small subset: the AI query endpoint for narrative, structured interpretation, and the V2 computation endpoints when you want raw chart data to drive your own layout. The base URL is https://api.vedika.io and every authenticated call carries an x-api-key header with a key in the vk_live_* format.

The birth-details contract

The v1 query endpoint nests birth data under birthDetails. The V2 computation endpoints take the same four fields flat. Either way, the fields that matter are datetime, latitude, longitude, and timezone. Get the coordinates and timezone right: they set the ascendant and the house cusps, and an off-by-one timezone or swapped sign on a coordinate moves the entire chart.

A minimal report request

Here is the smallest call that produces an interpreted, report-style answer. Swap in the question that frames your report section—a full marriage report might fan this out into several focused questions, each becoming a chapter.

curl -X POST https://api.vedika.io/api/v1/astrology/query \
  -H "x-api-key: vk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "Provide a detailed marriage and relationship analysis.",
    "birthDetails": {
      "datetime": "1990-08-15T14:30:00",
      "latitude": 19.0760,
      "longitude": 72.8777,
      "timezone": "Asia/Kolkata"
    }
  }'

Add "speed": "fast" to the body when you want a lower-latency pass for high-volume sections; omit it for the deeper default response. Per-query cost runs roughly $0.01–$0.05 depending on the path, so a multi-chapter report is a predictable sum of its sections.

Driving your own PDF layout

If you prefer to typeset the document yourself, pull structured computation from V2 and feed it into your PDF generator. The example below sketches the pattern: fetch chart data, then assemble interpreted sections, then render.

const BASE = "https://api.vedika.io";
const headers = {
  "x-api-key": process.env.VEDIKA_API_KEY,
  "Content-Type": "application/json",
};

const birth = {
  datetime: "1990-08-15T14:30:00",
  latitude: 19.076,
  longitude: 72.8777,
  timezone: "Asia/Kolkata",
};

// 1. Raw chart data for your own page layout
const chart = await fetch(`${BASE}/v2/astrology/chart`, {
  method: "POST",
  headers,
  body: JSON.stringify(birth),
}).then((r) => r.json());

// 2. Interpreted chapters, one call per section
async function chapter(question) {
  const res = await fetch(`${BASE}/api/v1/astrology/query`, {
    method: "POST",
    headers,
    body: JSON.stringify({ question, birthDetails: birth }),
  });
  return res.json();
}

const sections = await Promise.all([
  chapter("Summarize career and profession indications."),
  chapter("Analyze wealth and financial prospects."),
  chapter("Assess health tendencies and timing."),
]);

// 3. Hand `chart` + `sections` to your PDF renderer
// (e.g. a server-side HTML-to-PDF step with your branded template)

Because the narrative endpoint is the same one that powers conversational queries, you can mix report generation and live Q&A on a single integration and a single key.

Three systems, one input

A real differentiator for report products is breadth. The same birth details can drive a Vedic (sidereal) report, a Western (tropical) natal report, or a KP report, all from one API—so you can offer all three to different audiences without integrating three vendors. Beyond the big three, the platform also computes Jaimini, Tajaka (annual / Varshaphal), Lal Kitab, and numerology, which map cleanly to distinct report SKUs.

Interpretations follow the classical curriculum that practicing astrologers are actually trained on. Vedic readings trace to texts such as Brihat Parashara Hora Shastra and Phaladeepika; KP readings to Krishnamurti's KP Readers; Western readings to Ptolemy's Tetrabiblos. That sourcing discipline is what keeps a report defensible when a domain expert reads it.

Multilingual deliverables

Reports and narrative responses are available in 30 languages, including 14 Indic languages. For a consumer-facing astrology product, shipping a Hindi or Tamil report from the same endpoint as the English one—no separate translation pipeline—is often the feature that wins the market you're targeting.

Why the chart underneath the report holds up

A report is only as trustworthy as the chart it is built on. The placements come from the XALEN Ephemeris, Vedika's own open-source astronomical engine (Apache-2.0, published to crates.io, PyPI, and npm, with around 2,200 tests). It has been validated against JPL DE440 and swetest, with zero charts deviating beyond 0.1° across a reproducible JPL DE440 benchmark set. That is astronomical precision—the planetary positions and angles—not a claim about interpretive accuracy, which remains a matter of classical tradition and astrologer judgment.

The practical payoff: because the ephemeris is open and reproducible, you can independently verify any placement that appears in a report rather than trusting an opaque black box.

How this compares to other report APIs

Several established providers serve astrology data. Prokerala (around $19) is a long-standing, well-documented option with strong Vedic coverage; AstrologyAPI.com (around $29) offers a broad catalog of report endpoints; RoxyAPI (around $39) is another solid data source. These are real choices and worth evaluating against your needs.

Where Vedika is structurally different: three systems plus the specialized tracks under one key, an open-source ephemeris you can audit, source-traceable interpretations, 30-language output, and the first public astrology MCP server (npx @vedika-io/mcp-server, 36 tools) so an LLM agent or MCP-compatible client can request a report directly. Plans run from Starter at $12/mo to Professional $60, Business $120 (with fast-path and voice), and Enterprise $240, with per-query pricing of $0.01–$0.05.

Key facts

• Report narrative endpoint: POST /api/v1/astrology/query; streaming variant at /api/v1/astrology/query/stream; base URL https://api.vedika.io.
• Auth is an x-api-key header with a vk_live_* key; per-query cost is roughly $0.01–$0.05.
• One API covers Vedic (sidereal), Western (tropical), and KP, plus Jaimini, Tajaka, Lal Kitab, and numerology.
• Output is available in 30 languages (14 Indic) and is white-label-ready for resale.
• Placements come from the open-source XALEN Ephemeris, validated against JPL DE440 with no chart deviating beyond 0.1° across a reproducible JPL DE440 benchmark.
• 700+ operations across 25 domains; free sandbox testing requires no key.

Getting started

Prototype the request and response shapes in the free sandbox first—no key needed—so you can confirm the report fields you want before writing a line of production code. When you're ready, review the API docs for the full endpoint catalog and pick a plan on the pricing page. If you're integrating AI-driven generation, the astrology MCP server guide shows how an LLM agent can request reports on demand.

FAQ

Can I white-label the PDF reports with my own brand?

Yes. Reports are designed for resale: you can apply your own cover, logo, and color theme so the deliverable carries your brand rather than Vedika's. The API returns a generated document you host and distribute under your product.

Which astrology systems do the reports cover?

One API serves Vedic (sidereal), Western (tropical), and KP from the same birth input, plus specialized tracks such as Jaimini, Tajaka (annual), Lal Kitab, and numerology. You choose the report type per request.

Are the interpretations sourced from classical texts?

Every astrological claim is attributable to classical sources used in formal Jyotish, KP, and Western training, such as Brihat Parashara Hora Shastra, Phaladeepika, and Ptolemy's Tetrabiblos. Computed placements come from the in-house XALEN Ephemeris engine.

How are reports priced?

Reports draw from your wallet balance on a per-generation basis, with plans starting at $12/mo for Starter. You can prototype the request and response shapes for free in the sandbox before adding a key.

What birth details do I need to send?

A datetime, latitude, longitude, and timezone identify the chart. Accurate coordinates and timezone matter most, since they set the ascendant and house cusps that the report is built on.