Agent Platform1

AI & MCP7

AI Interpretations5

AI Reports5

Aspects & Points11

Astro-Geography18

BaZi (Four Pillars)11

Business Astrology12

Calendar & Cycles15

Chinese: Zodiac & Feng Shui14

Comparisons10

Content Localization4

Core4

Cosmobiology / Hamburg School10

Destiny Matrix1

Dignities & Receptions6

Elder Futhark Runes5

Embeddable Widgets14

Esoteric17

Evolutionary Astrology5

Family Astrology5

Financial Astrology10

Geomancy (Agrippa)16

Hellenistic: Brennan tradition10

Hellenistic: Greenbaum tradition10

Hellenistic: Hand tradition10

Hellenistic: Schmidt tradition10

Horary6

Horoscope5

Human Design12

I Ching (Standalone)5

Kabbalah3

Mayan Calendars8

MCP Advanced5

Modern Psychological15

Numerology: Chaldean10

Numerology: Kabbalistic (Mathers strict)10

Numerology: Kabbalistic (phonetic)10

Numerology: Pythagorean10

Numerology: Vedic10

Palmistry (Cheiro)5

Pet Astrology14

Prognostics15

Public9

Real-time Streaming10

Reference14

Reports18

Specialized Charts5

System6

Tarot: Lenormand10

Tarot: Marseille21

Tarot: Rider-Waite-Smith35

Vedic174

Visualization14

Webhooks15

Wellness10

White-label5

Zi Wei Dou Shu (Purple Star): MVP13

Zodiac Signs (Per-Sign Deep)12

Comparisons

Synastry Aspect Grid

NxM matrix of cross-chart aspects between the two charts (default 13×13: Sun..Pluto + nodes + Lilith + Chiron). Cells contain aspect or null.

post/synastry/aspect-grid

Request body

Response

Successful calculation

okboolean

Example response

{
  "ok": true
}

Changes

Changed in 4 of the 13 revisions of this API.131412

Aug 24, 20268ab5a768b521526See the full diff
- ▲
  the response property data/bodies1/items/ became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property data/bodies2/items/ became nullable for the status 200
  response-property-became-nullable
- ▲
  the data/bodies1/items/ response's property type/format changed from / to object/ for status 200
  response-property-type-changed
- ▲
  the data/bodies2/items/ response's property type/format changed from / to object/ for status 200
  response-property-type-changed
- ▲
  the data/grid/items/items/ response's property type/format changed from object/ to / for status 200
  response-property-type-changed
- ●
  removed the optional property data/grid/items/items/orb from the response with the 200 status
  response-optional-property-removed
- ●
  removed the optional property data/grid/items/items/type from the response with the 200 status
  response-optional-property-removed
- ○
  added the optional property data/bodies1/items/id to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/bodies1/items/longitude to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/bodies1/items/name to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/bodies2/items/id to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/bodies2/items/longitude to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property data/bodies2/items/name to the response with the 200 status
  response-optional-property-added
Aug 18, 2026dd3764875e7a2See the full diff
- ○
  added the new optional request property chart1/ayanamsa
  new-optional-request-property
- ○
  added the new optional request property chart2/ayanamsa
  new-optional-request-property
Aug 15, 2026e637d1a9911b4See the full diff
- ●
  the chart1/timezoneOffset request property's max was set to 14.00
  request-property-max-set
- ●
  the chart2/timezoneOffset request property's max was set to 14.00
  request-property-max-set
- ●
  the chart1/timezoneOffset request property's min was set to -14.00
  request-property-min-set
- ●
  the chart2/timezoneOffset request property's min was set to -14.00
  request-property-min-set
Aug 11, 2026b0533bcc12c0884See the full diff
- ▲
  the request property chart1/latitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property chart1/longitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property chart2/latitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property chart2/longitude became not nullable
  request-property-became-not-nullable
- ▲
  the request property chart1/latitude became required
  request-property-became-required
- ▲
  the request property chart1/longitude became required
  request-property-became-required
- ▲
  the request property chart2/latitude became required
  request-property-became-required
- ▲
  the request property chart2/longitude became required
  request-property-became-required
- ●
  the chart1/latitude request property's max was set to 90.00
  request-property-max-set
- ●
  the chart1/longitude request property's max was set to 180.00
  request-property-max-set
- ●
  the chart2/latitude request property's max was set to 90.00
  request-property-max-set
- ●
  the chart2/longitude request property's max was set to 180.00
  request-property-max-set
- ●
  the chart1/latitude request property's min was set to -90.00
  request-property-min-set
- ●
  the chart1/longitude request property's min was set to -180.00
  request-property-min-set
- ●
  the chart2/latitude request property's min was set to -90.00
  request-property-min-set
- ●
  the chart2/longitude request property's min was set to -180.00
  request-property-min-set
- ○
  the latitude request property default value 0 was removed
  request-property-default-value-removed
- ○
  the latitude request property default value 0 was removed
  request-property-default-value-removed
- ○
  the longitude request property default value 0 was removed
  request-property-default-value-removed
- ○
  the longitude request property default value 0 was removed
  request-property-default-value-removed

Full history