/api/astro/muntha/1 creditMuntha (varshaphal)
The Muntha for a varshaphal year: its sign, and the house it falls in within that year's annual chart. The Muntha begins at the natal ascendant and advances ONE SIGN PER COMPLETED YEAR, so it returns to where it started every twelfth year. Its house, though, is counted from the ANNUAL (varshapravesh) ascendant rather than the natal one - and that ascendant moves each year - which is why two years sharing a Muntha sign will usually not share its house. Both ascendants are returned so the count can be checked. `year` is optional and defaults to the native's current solar-return year. `age_completed` is the number of solar returns that have passed, which is what the advance is counted from - a running year does not move the Muntha.
https://api.occultapi.com/api/astro/muntha/Authentication
Send your key in the X-API-Key header. Keys are server-side credentials — never put one in browser JavaScript or a mobile app.
X-API-Key: yt_live_a1b2c3d4_…
Content-Type: application/jsonRequest fields
| 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. |
| 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 |
| ayanamsa | string | optional | |
| timezone_as_float | number (double) | optional | UTC offset of the place, in hours, as a decimal. Example: 5.5 for India (UTC+05:30), -5 for New York in winter, 5.75 for Nepal. This is NOT validated against date_time - if the two disagree you get a successful response for the wrong moment, so derive both from the same source. Use the offset in force on that date, not today's: a summer birth in a country with daylight saving needs the summer offset. min -12 · max 14 |
| year | integer | optional | Year of birth as a number, e.g. 1990. Four digits. min 1900 · max 2200 |
Example request
This example is not yet verified
The field names and types below are taken from the API definition and are accurate, but this particular body has not returned a success when we last ran it — it may need a value we cannot infer. Treat it as a starting point rather than a working command.
curl -X POST https://api.occultapi.com/api/astro/muntha/ \
-H "X-API-Key: $OCCULT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date_time":"2026-09-01 06:00:00","latitude":26.9124,"longitude":75.7873,"timezone_as_float":5.5,"year":2026}'Response
A verified example response is not available for this endpoint yet. The request shape above is generated from the API definition and is accurate; we publish response samples only once we have proven them against a live call.
Errors
Metering errors return { "error": "…", "message": "<code>", "is_error": true }. Show error to people and branch on message. See the error reference.