Overview
If your app already has a user’s name and date of birth for astrology features, you have everything a numerology profile needs. The core endpoint turns that same input into numbers you can show alongside the chart. Examples use Aarav Sharma, born 1990-08-15.
This is an integration walkthrough. See Documentation for exact fields, systems, and plan gates.
Keep Numerology Distinct
Numerology and horoscope are different systems with different inputs and methods. Present them as separate sections, and never label a numerology number as an astrological one. Numerology comes from the numerology endpoints; charts come from the Horoscope API. Keeping them apart avoids confusing users and keeps each result accurate to its own tradition.
You can reuse the stored name and date for both features, but compute and display them independently. A shared input does not mean a shared calculation.
Adding a Numerology Profile
Call the core endpoint with the user’s name, date, and your chosen system:
curl -X POST https://panchang.devdarsha.com/v1/numerology/core \
-H "content-type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{"name":"Aarav Sharma","date":"1990-08-15","system":"pythagorean"}'Cache the profile against the name, date, and system. Because the calculation is deterministic, you only need to compute it once per user unless their input changes.
How to Present It
A common layout is a “Numbers” tab or card next to the chart, showing the life path and a few name numbers with clear labels. Decide once how you display master numbers, and show the system so users know which tradition produced each value.
Rollout Planning
Estimate one core call per user profile, plus occasional recomputes. Test representative names and dates in Playground, confirm your UI handles optional or plan-gated fields, and store the X-Request-ID for support cases.