Ascendant & Rising Sign Calculation

What is the Ascendant Report endpoint?

You need the rising sign for a birth and a ready-to-display interpretation that goes with it. The Ascendant Report endpoint takes birth data (date, time, place) and returns the exact ecliptic position of the Ascendant, the zodiac sign it falls in, and a multi-paragraph personality reading written in plain prose for that specific sign.

This endpoint is part of the Natal Chart API.

Why does this endpoint exist?

You are surfacing rising-sign content and you want both the calculation and the interpretation in one call. Computing the Ascendant takes the same Swiss Ephemeris stack as Planetary Positions. Writing twelve sign-specific reading variants takes weeks. This endpoint hands you both: the calculated rising sign and the matching interpretive text in any of twelve languages.

What inputs does it need?

You pass standard birth data: API key, full name, date components, time components, gender, place, decimal latitude and longitude, and timezone offset. Birth time precision matters here more than for sun-sign features: the Ascendant changes roughly every two hours, so a wrong time gives a wrong rising sign. Authentication uses a Bearer token in the Authorization header.

What does the response data look like?

You get back a data object with five fields: the rising sign, its number, the exact ecliptic degree, the sign-relative position, and a multi-paragraph interpretive reading. The reading is plain text with \n\n paragraph breaks, ready to render directly into your UI.

The result field is locale-aware: pass lan="hi" to get the reading in Hindi, lan="es" for Spanish, and so on across the twelve supported languages.

What does a real response look like?

Below is the response for a sample birth (24 May 2023, 14:40:43 IST, New Delhi) with Libra rising at 5°43'. The result field is truncated for readability; the live response runs roughly 2 KB of prose.

{
  "success": 1,
  "data": {
    "sign": "Libra",
    "sign_no": 7,
    "full_degree": "185.7194554",
    "longitude": "5:43:10",
    "result": "If you have Libra ascendant, you possess a charming and diplomatic personality. You have a natural ability to create harmony and balance in your interactions with others.\n\nYour gracious and polite demeanor makes you well-liked by those around you. You have a genuine interest in people and enjoy forming meaningful connections... (truncated, ~2 KB total)"
  }
}

What can you build with this endpoint?

You use the Ascendant Report whenever your product needs the rising sign with reader-facing context, not just the raw degree. The single response covers both the calculation and the copy, which makes it a natural fit for profile pages, onboarding flows, and localized content engines.

1. Birth chart profile pages. Show "Your Rising Sign: Libra" with the interpretive reading directly underneath.
2. Onboarding flows. Surface the Ascendant on the first profile screen as the most "personal" astrological signature, since it depends on exact birth time.
3. Localized content engines. Toggle lan per user locale to ship rising-sign content in the user's language without maintaining a translation pipeline.
4. Ascendant comparison features. Call the endpoint for two birth charts side by side for "your rising sign vs theirs" relationship insights.

How accurate is the calculation?

You are reporting a sign that depends on minute-level birth time precision, so accuracy starts at the data layer. The Ascendant is calculated by Swiss Ephemeris using NASA JPL ephemeris data, the same engine used by Planetary Positions and House Cusps. The returned full_degree is accurate to arc-second precision.

Birth time accuracy matters disproportionately. The Ascendant cycles through all twelve signs every 24 hours, so a 30-minute time error can shift the rising sign by half a sign. If birth time is unknown, treat the result as approximate and surface that caveat in your UI.

How does this relate to the parent API?

You are building a rising-sign feature, and this endpoint covers both the calculation and the prose. This endpoint complements the Natal Chart API by providing the rising sign together with a ready-to-display interpretation.

Planetary Positions and House Cusps both return the Ascendant degree as a raw value, but neither includes interpretive copy. Use this endpoint when your UI needs the readable text alongside the data, and use the lower-level endpoints when you only need the degree for chart rendering.

Summary

The Ascendant Report endpoint returns the rising sign, its exact ecliptic degree, and a multi-paragraph interpretive reading for any birth datetime. It runs on Swiss Ephemeris with NASA JPL ephemeris data, supports twelve languages via the lan parameter, and ships data plus copy in a single response. Use it whenever your product surfaces the rising sign with reader-facing prose, not just a raw value.