Skip to content

Relationship Endpoints

The Relationship category helps apps model interpersonal dynamics using numerology-driven compatibility patterns. Use these routes for couple insights, healing workflows, and family connection reports.

Direct API Access Required

Endpoints in this category are available on the direct Numerology API platform only. They are currently not supported via RapidAPI. Base URL: https://api.numerologyapi.com

Authentication & Access

  • Auth header: X-API-Key: YOUR_API_KEY
  • Input model: use both participants' details when required for composite analysis
  • Practical tip: normalize names and date formats before scoring compatibility

Available Endpoints

  • Relationship Composite Build a combined compatibility profile from two numerology signatures.
  • Relationship Healing Reading Generate guidance focused on repair, communication, and emotional recovery.
  • Parent Child Numerology Interpret parent-child energetic dynamics and growth opportunities.

  • Team Dynamics Numerology Analyze team, founder group, board, or project-group vibration from member names and birth dates.

  • Relationship Milestone Numerology The Relationship Milestone Numerology endpoint reads two people, their birth dates, and a relationship date to produce a milestone-specific resonance report. It is part of the v1.0.2 preparation set and uses the expanded 26-locale meaning bundles.
  • Family Legacy Matrix The Family Legacy Matrix endpoint builds a family-system report from a surname, member names, birth dates, and roles. It is part of the v1.0.2 preparation set and uses the expanded 26-locale meaning bundles.
  • Pet Name Harmony The Pet Name Harmony endpoint reads a pet name, pet date, and household members to create a symbolic companion and household-fit report. It is part of the v1.0.2 preparation set and uses the expanded 26-locale meaning bundles.

Implementation Notes

  • Combine with Core Endpoints to expose each person’s baseline numbers before composite interpretation.
  • Pair with Spiritual & Shadow Endpoints for deeper relational self-awareness.
  • In product UX, separate "profile summary" from "actionable guidance" for higher readability.

Open Dashboard