curl -X POST https://yogataraapi.prahlad.app/api/astro/general_prediction/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keys":["get_prediction_details"],"date_time":"2025-07-09T10:26:45.109Z","latitude":26.9124,"longitude":75.7873,"timezone":0}'A written character-and-life reading assembled from a birth chart: the temperament of the moon sign, what each of the nine planets means in the house it occupies, and what each of the twelve house lords means in the house it has gone to. It is the narrative counterpart to /api/astro/chart_analysis/, which returns much the same structure as data. The text is drawn from published sources — the moon sign section cites B. V. Raman's How to Judge a Horoscope for one reading and a second source for the other — so the same chart always produces the same prose. Send the birth moment, place and UTC offset; there are no other options. Everything comes back as HTML fragments with bold headings and line breaks, ready to drop into a page. Note that this endpoint calls the UTC offset field `timezone`, not `timezone_as_float`.
| Field | Type | Required | Notes |
|---|---|---|---|
| date_time | string (date-time) | required | The moment to calculate for, ISO 8601. ALWAYS include an offset or a trailing Z - a value with no zone is read as Asia/Kolkata (UTC+05:30), not UTC, and can return the previous day's result with a 200. '2026-09-01T06:00:00Z' and '2026-09-01 06:00:00' are different instants and give different answers. FORMAT constraint. DRF DateTimeField: ISO-8601 only (DRF default input formats), e.g. "2026-09-01T06:00:00+05:30", "2026-09-01T06:00:00Z" or "2026-09-01 06:00:00" (no timezone = UTC assumed). |
| keys | array | required | Which calculations to return, as a list of names. See the key table for this endpoint; an unrecognised name rejects the whole request. One call costs one credit however many keys you ask for, so request everything you need at once rather than making several calls. get_prediction_detailsArray of strings; only one key exists. |
| latitude | number (double) | required | Latitude of the place, in decimal degrees. Positive is north, negative is south. Example: 26.9124 for Jaipur, 40.7128 for New York. Minutes and seconds are not accepted - convert first. min -90 · max 90 |
| longitude | number (double) | required | Longitude of the place, in decimal degrees. Positive is east, negative is west. Example: 75.7873 for Jaipur, -74.0060 for New York. Note the sign: a missing minus puts New York in China. min -180 · max 180 |
| timezone | number (double) | required | UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30). Identical in meaning to timezone_as_float, which other endpoints call the same thing by a different name. |
Ask for exactly the calculations you want by listing them in keys. An unknown key rejects the whole request, and you are charged 1 credit however many you ask for — so batch them.
| Key | Extra fields needed | Description | |
|---|---|---|---|
| get_prediction_details | — | The full written reading, as an object of four HTML strings. 'Janma rasi_1' and 'Janma rasi_2' give two independent readings of the moon sign's mental, physical and general tendencies; 'Planets' walks all nine planets through the house each occupies, counted from the ascendant; 'Houses' walks all twelve house lords through the house they occupy. Each value is a single HTML fragment with bold sub-headings. |