Overview
Two endpoints produce the core numbers: /v1/numerology/core, which returns the full profile from a name and date, and /v1/numerology/name, which focuses on name-derived numbers. Examples use Aarav Sharma, born 1990-08-15.
Use this to understand the number fields and how the system affects them. See Documentation for the complete schema and every reported number.
Date Numbers
Date-derived numbers come from the birth date and are reported under data.date_numbers:
life_path_number: the reduced total of the full birth date, the most commonly displayed number.moolank: the Ank Jyotish root number from the day of birth.bhagyank: the Ank Jyotish destiny number from the full date.
Name Numbers
Name-derived numbers, such as the expression number, come from mapping the letters of the name using the selected system. Each name number is reported with the system that produced it — Pythagorean or Chaldean — so the same name can be shown under either system without ambiguity. Call the name endpoint when you only need these:
curl -X POST https://panchang.devdarsha.com/v1/numerology/name \
-H "content-type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{"name":"Aarav Sharma","system":"chaldean"}'Master Numbers
When a total lands on 11, 22, or 33, it is treated as a master number and is not reduced away by default. The response reports the master value, and its reduced form where relevant, so your UI can show whichever your audience expects. Decide once how you present master numbers and apply it consistently.
Name numbers differ between Pythagorean and Chaldean. Send the system explicitly on every request so a profile is never computed under a system your product did not intend.
How to Use the Core Numbers
For a full profile screen, call the core endpoint once and read both the date numbers and the name numbers from a single response. Cache the result against the name, date, and system, since the calculation is deterministic. Render each number with a clear label and, where relevant, the system it came from.