Natal Wheel Chart Data

What is the Natal Wheel Chart endpoint?

You need a renderable birth chart for your UI. The Natal Wheel Chart endpoint takes birth data and returns the chart as both a complete SVG markup string and a base64-encoded SVG, ready to paste into an <img> tag or embed inline. You control colors, glyph style, and layout via request parameters.

This endpoint is part of the Natal Chart API.

Why does this endpoint exist?

You are shipping a chart visualization and you do not want to draw twelve houses, sixteen planets, and dozens of aspect lines yourself. The endpoint hands you a finished image computed from the same Swiss Ephemeris data that powers Planetary Positions and House Cusps. You skip the SVG drawing logic and focus on UX instead.

What inputs does it need?

You pass standard birth data plus styling parameters that control the wheel's appearance. The chart uses the same house_system parameter as the rest of the catalog. Authentication uses a Bearer token in the Authorization header alongside the body's api_key.

What does the response data look like?

You get a small envelope with two payloads of the same image. The svg field is the full inline SVG markup. The base64_image field wraps the same SVG in a data:image/svg+xml;base64,... URL ready for <img src>.

Pick whichever fits your rendering pattern: inline SVG for DOM access (hover, click handlers), or the base64 URL for a simple drop-in <img src>.

What does a real response look like?

Below is the response shape for a sample birth (24 May 2023, 14:40:43 IST, New Delhi). Both fields are truncated for readability; the real values run roughly 78 KB for svg and 105 KB for base64_image.

{
  "success": 1,
  "data": {
    "svg": "<svg height=\"400\" width=\"400\" xmlns=\"http://www.w3.org/2000/svg\"> ...truncated, ~78 KB of SVG markup... </svg>",
    "base64_image": "data:image/svg+xml;base64,PHN2ZyBoZWlnaHQ9IjQwMCIgd2lkdGg9IjQwMCIg...truncated, ~105 KB of base64-encoded SVG..."
  }
}

What can you build with this endpoint?

You use the Natal Wheel Chart whenever your UI needs a visual birth chart, either as a hero element on a profile page or as part of a generated PDF report. The endpoint covers the full rendering pipeline so you can integrate without owning any drawing code.

1. Profile pages and dashboards. Drop the base64_image into an <img> tag. Cache the response per user; the chart never changes.
2. Inline interactive charts. Inject the svg into the DOM and bind hover or click handlers to planet groups for tooltips.
3. PDF reports. Embed either field in your PDF template (most renderers handle base64 URLs natively) for downloadable deliverables.
4. Themed charts. Pass brand hex colors via wheel_color, text_color, and the background parameters so the chart matches your design system.

How accurate is the calculation?

You are rendering positions that downstream interpretations will reference, so accuracy and tunability both matter. The wheel chart pulls from the same Swiss Ephemeris and NASA JPL ephemeris data the Planetary Positions and House Cusps endpoints use. Planet positions are accurate to arc-second precision; house cusps follow the system you specified.

For births at extreme latitudes (above roughly 66 degrees) where Placidus becomes unstable, choose Whole Sign (W) or Equal House (E). The rendered layout adjusts automatically.

How does this relate to the parent API?

You are building the visual layer of a birth chart feature. This endpoint complements the Natal Chart API by providing a ready-to-render wheel chart computed from the same source data as Planetary Positions, House Cusps, and the Aspect Table.

If you only need the visual, this endpoint alone is enough. For custom overlays (tooltips, interpretation panels, transit lines), call Planetary Positions and House Cusps in parallel for the structured data and use this endpoint for the base image.

Summary

The Natal Wheel Chart endpoint returns a complete birth chart as both inline SVG and base64-encoded SVG, computed on Swiss Ephemeris. You control colors, glyph display, and house system via request parameters. Use it whenever your product needs a visual chart without owning the rendering pipeline. Pair with Planetary Positions, House Cusps, and the Aspect Table when you need structured data alongside.