You can give every customer a full astrology report under your own name with one API call. This is often called a white-label report. Send the birth details to POST /v1/report with your heading in the title option. The answer is a complete report as one HTML page. It carries your heading, and no logo, name or link of ours. Print it to PDF in any browser, and it is ready to hand over.
A good customer report has three parts. First, the chart, with the facts it was built on. Second, the planetary periods running now, with dates. Third, readings in plain words that a customer can follow without knowing astrology.
The API writes the chart chapters, names the running periods and writes every reading. You add four things: your cover and logo, a chart drawing, the period dates and the PDF step. On the Free plan, you also add a "Powered by API for Astrology" link wherever the report appears. Paid plans need no link.
Below is a real report we made for John Doe, born Aug 15, 1990, 10:30 AM, in New York. It shows each part.
What one report call returns
POST /v1/report takes the same birth details as a chart call. It sends back a full reading as a single page of HTML (the code behind every web page). We ran it for John Doe on Oct 13, 2026, with the heading "Acme Inc. Birth Chart Report for John Doe".
The page we got back had 11 chapters and about 32,000 words. It used no scripts, images, web fonts or files from anywhere else, so it opens without an internet connection. It had print styles built in. It had no links at all.
The top of the page is a short facts table. It shows the lagna (the sign rising in the east at birth), the Moon sign and the time zone. It also names the zodiac offset, the house system and the planet data source. For John, that is Virgo rising, a Taurus Moon and UTC-4. New York was on daylight saving time that day.
Every paragraph in the report is the same text that the single reading sections return. So the report never disagrees with the screens in your app. Our post on readings from one computation explains why that matters.
What a good customer report contains
A report is for a customer who does not read charts. Here is what each part does, and where it comes from in John's report.
Part of the report | What the customer gets | Chapter in the API's report |
|---|---|---|
The chart and its facts | The rising sign, the Moon sign, the birth star and how they were found | Facts table, Your birth details, The chart |
A summary in plain words | Strengths, what takes effort, and small daily picks such as a best day and colors | In plain words, Your signature |
Planets and houses | What each planet and each of the 12 life areas means for this person | The grahas, The houses |
Mixed signals | Where two rules in the chart point different ways, with both sides | Where your chart disagrees with itself |
Yogas | Special planet combinations the chart forms | What the chart forms |
The periods running now | The main period, the sub-period and the period inside that | Your periods |
Planet movements now | How today's planet positions touch the birth chart | What is moving now |
Life topics (optional) | Career, love, money, education and more | The topic readings |
An honest gap list | Combinations with no text written yet | What is not here |
The last row helps your support team. John's chart has 4 planets in Cancer: the Sun, Jupiter, Venus and Ketu. The written text covers pairs and triples of planets, not groups of 4. So the report lists that group under "What is not here" instead of skipping it. A customer who asks "why does my report not mention this?" gets a clear answer on the page.
Your brand: what the API sets and what you add
The API sets one brand element: the heading. Whatever you send as title becomes the big heading at the top. It is also the page title in the browser tab. When you send no title, the heading is the rising sign. John's untitled report was headed "Virgo Ascendant".
Everything else about the brand is yours, because the page carries nothing of ours. Here is what you add.
Your cover and logo. Show the report inside your own page, under your logo and colors. For a PDF, put your own cover page in front of it before you print.
A drawing of the chart. The report has no images, so it has no chart picture. Your app draws the chart in the North or South Indian style your customers know. The positions come from POST /v1/planets, as our kundli API page shows.
A page of period dates. The report names the running periods but does not list their dates. The next section shows how to add them.
The PDF. Print the page to PDF from any browser. To make PDFs without a person, run the page through a headless browser on your server. That is a browser with no screen.

A real report for John Doe
This is the call behind our example. The as_of date turns on the chapters about planet movements now.
_John Doe, born Aug 15, 1990, 10:30 AM, New York (America/New_York)_
curl -X POST "https://apiforastrology.com/api/astrology/v1/report?title=Acme%20Inc.%20Birth%20Chart%20Report%20for%20John%20Doe&as_of=2026-11-17" \
-H "Authorization: Bearer $ASTROLOGY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"year":1990,"month":8,"day":15,"hour":10,"minute":30,"second":0,"latitude":40.7128,"longitude":-74.006,"timezone":"America/New_York"}'The answer is the HTML page itself. This is its first part, trimmed, as our API returned it on Oct 13, 2026.
_John Doe, born Aug 15, 1990, 10:30 AM, New York: the top of the report_
<title>Acme Inc. Birth Chart Report for John Doe</title>
...
<h1>Acme Inc. Birth Chart Report for John Doe</h1>
<table class="facts">
<tr><th>Ascendant</th><td>Virgo</td></tr>
<tr><th>Moon sign</th><td>Taurus</td></tr>
<tr><th>Timezone used</th><td>UTC-4:00 (America/New_York, EDT)</td></tr>
<tr><th>Ayanamsa</th><td>lahiri (23.726073)</td></tr>
<tr><th>Houses</th><td>whole sign, counted from the ascendant</td></tr>
<tr><th>Ephemeris</th><td>JPL DE440s</td></tr>
</table>
<h2>In plain words</h2>
<h3>In short</h3>
<p>You are practical first. You want to know how something actually works, ...</p>Look at the readings. "You are practical first" needs no astrology to understand. The full text of a report like this one is on our sample report page, chapter by chapter.
Add a dated timeline of periods
A dasha is a period of life ruled by one planet. A page of period dates answers a plain question: "Which period am I in, and when does it end?"
John's report, made for Nov 17, 2026, names three running periods. They are the Jupiter mahadasha (main period), the Moon antardasha (sub-period) and the Saturn period inside that. The dates come from one more call, POST /v1/dasha/vimshottari, with levels set to 3.
Level | Planet | Starts | Ends |
|---|---|---|---|
Main period | Jupiter | Dec 20, 2014 | Dec 20, 2030 |
Sub-period | Moon | Apr 21, 2026 | Aug 21, 2027 |
Third level | Saturn | Nov 14, 2026 | Jan 30, 2027 |
Put this table on its own page, right after your cover. It answers that question before the customer reads a chapter. The dasha API page lists every field the call returns.
See a full report first. Open the sample report for John Doe. It lists every chapter and every option in one place.

Language, length and topics
Four more options change what the customer gets. Each one is a query option on the same call.
Option | What it does | What we saw for John Doe |
|---|---|---|
| Writes the report in Hindi | Hindi heading and chapters, such as "आसान शब्दों में" for "In plain words" |
| Longer text in each passage | About 58,000 words instead of about 32,000, which is 1.8 times longer |
| Adds planet movements for a date | Without it, the report had 10 chapters, with no "What is moving now" |
| Adds the life topic readings | A 12th chapter, "The topic readings" |
Your heading can be in Hindi too. We sent "Acme Inc. जन्म कुंडली रिपोर्ट" as the title, and it came back as the heading as written.
For a puja store, this means one call per customer, in the customer's language. The puja stores page covers the dosha, panchang and festival calls a store uses alongside it. A consultancy can send each client a report after a session. The astrologer platforms page shows that setup.
What a report uses, and the one plan rule
A report is a written reading, so it uses reading credits, not calls. One full report uses 25 reading credits. With topics=true, it uses 40. Hindi and expanded text cost the same as English and standard text.
Test keys use no credits. They return reports only for the two sample charts, John Doe and Jane Doe. That is enough to build and check your cover, layout and PDF step before real customers arrive.
One plan rule touches your brand. On the Free plan, a live product must show a visible "Powered by API for Astrology" link. It goes wherever the product shows API output. So a report shown on the Free plan needs that link on the same page or screen. Paid plans need no link. Test keys need none either.
Ready to build? Read what each reading call returns on the reading and report API page. Then try POST /v1/report in the API reference.

A short checklist before you send the first one
Run through these with John Doe on a test key before you go live.
Check | What good looks like |
|---|---|
Heading | Your brand and the customer's name, sent as |
Facts table | Rising sign, Moon sign and the right time zone for the birth date |
Period page | The running main period, sub-period and third level, with dates |
Chart drawing | Drawn by your app from |
Language |
|
Planet movements |
|
Credit link | Shown next to the report if you are on the Free plan |
A branded report is the same reading the API writes for anyone. Your heading, your cover, your chart drawing and your page of dates make it yours.



