Aspect Table Generation for Natal Charts

What is the Aspect Table endpoint?

You need to know which planets in a chart are talking to each other and how. The Aspect Table endpoint takes birth data and returns every pairwise angular relationship between planets, the Ascendant, and the Midheaven. Each entry tells you which two bodies are in aspect, what kind of aspect, and how exact it is in degrees.

This endpoint is part of the Natal Chart API.

Why does this endpoint exist?

You are interpreting a birth chart and you need the dynamic relationships, not just the static positions. Calculating which angles count as aspects, and how loosely they should match, means iterating every planet pair, applying orb tolerances, and filtering by aspect category. This endpoint does that work in one call.

What inputs does it need?

You pass the same birth data as every Natal Chart endpoint, plus two filters that control which aspects you get back: aspects_type (which categories) and orb_mode with optional orb settings (how loose the angular match has to be). Authentication uses a Bearer token in the Authorization header alongside the body's api_key field.

Major aspects cover Conjunction, Sextile, Square, Trine, and Opposition. Minor covers Semisextile, Semisquare, Sesquiquadrate, Quincunx, Quintile, Biquintile, Novile, and Septile. Pass a custom list like "CONJUNCTION,TRINE,SQUARE" to narrow further.

What does the response data look like?

You get back an envelope with a success flag and a data array of aspect objects. Each object names the two bodies involved, the aspect type, and the orb (the deviation from an exact angular match, in degrees). A tighter orb means the aspect is closer to perfect.

Ascendant and Midheaven aspects appear alongside planet-to-planet relationships in the same array.

What does a real response look like?

Below is a slice of the Aspect Table response for a sample birth (24 May 2023, 14:40:43 IST, New Delhi). The full response returns every pairwise aspect; this slice shows ten major-aspect entries to keep the example readable.

{
  "success": 1,
  "data": [
    { "planetOne": "Sun", "planetTwo": "Moon", "aspect": "Sextile", "orb": 5.67 },
    { "planetOne": "Sun", "planetTwo": "Mars", "aspect": "Sextile", "orb": 0.83 },
    { "planetOne": "Sun", "planetTwo": "Saturn", "aspect": "Square", "orb": 3.76 },
    { "planetOne": "Sun", "planetTwo": "Neptune", "aspect": "Sextile", "orb": 5.66 },
    { "planetOne": "Sun", "planetTwo": "Pluto", "aspect": "Trine", "orb": 2.72 },
    { "planetOne": "Sun", "planetTwo": "Ascendant", "aspect": "Trine", "orb": 2.75 },
    { "planetOne": "Moon", "planetTwo": "Mars", "aspect": "Conjunction", "orb": 4.84 },
    { "planetOne": "Moon", "planetTwo": "Jupiter", "aspect": "Square", "orb": 4.43 },
    { "planetOne": "Moon", "planetTwo": "Saturn", "aspect": "Trine", "orb": 9.42 },
    { "planetOne": "Mars", "planetTwo": "Jupiter", "aspect": "Sextile", "orb": 0.41 }
  ]
}

What can you build with this endpoint?

You use the Aspect Table whenever your chart UI needs to show how planets interact, not just where they sit. Wheel charts, aspect grids, "tightest aspect" highlights, and any interpretation engine that comments on planet pairs all pull from this single response.

1. Wheel chart aspect lines. Draw a line between each pair on the zodiac wheel, color-coded by aspect category.
2. Aspect-grid component. Render the classic 12x12 aspect grid populated from this single response.
3. Tightest-aspect highlights. Sort by orb ascending to surface the chart's strongest patterns. An orb under 1 degree is usually the dominant signature.
4. Custom aspect filtering. Pass aspects_type="CONJUNCTION,OPPOSITION" to narrow to hard aspects, or toggle between major and minor views in your UI.

How accurate is the calculation?

You are surfacing aspect orbs that interpretive content depends on, so accuracy and tunability both matter. Aspect calculations run on Swiss Ephemeris with NASA JPL ephemeris data underneath, the same precision the Planetary Positions endpoint uses for the underlying degrees.

Orb tolerance is configurable. FIXED mode sets explicit degree-minute ranges per aspect category. PERCENTAGE mode adjusts default orbs by -90% to +100%. Default orbs are wider for major aspects (around 8 degrees) and tighter for minor aspects (1 to 3 degrees).

How does this relate to the parent API?

You are layering interpretation on top of raw positions. This endpoint complements the Natal Chart API by providing the pairwise aspect relationships between every planet, the Ascendant, and the Midheaven.

Planetary Positions tells you where each body sits. House Cusps tells you which life-area frame they occupy. The Aspect Table tells you how they interact. Together those three endpoints describe a birth chart geometrically, ready for visual rendering or text interpretation.

Summary

The Aspect Table endpoint returns every pairwise aspect in a birth chart with the two bodies, the aspect type, and the orb. You filter by aspect category and tune orb tolerance via FIXED or PERCENTAGE mode. Pair it with Planetary Positions and House Cusps to power wheel-chart aspect lines, aspect grids, and any interpretive feature that hinges on planetary relationships.