Overview
The /v1/numerology/name endpoint focuses on the numbers derived from a name, without needing a birth date. That makes it a good fit for tools where the name itself is what the user is exploring. Examples use the sample name Aarav Sharma.
This is an integration walkthrough for name-focused products. See Documentation for the full field list and systems.
The Name Endpoint
Send a name and the system you want. The response returns the name numbers under that system:
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"}'Because a name’s numbers differ between Pythagorean and Chaldean, present the system prominently so users know which tradition a result reflects.
How to Build a Name Tool
A typical flow:
- Accept one or more candidate names from the user.
- Call the name endpoint for each, under the system your product presents.
- Show the resulting numbers side by side so users can compare candidates.
- Cache each name’s result, since the calculation is deterministic.
For branding, the same pattern lets a user compare brand-name options and see the numbers behind each.
Framing the Results
Present name numbers as descriptive information for the user to weigh, alongside the ordinary considerations of a good name. Keep the copy factual and free of assurances about outcomes.
The /name-correction endpoint is live on the Pro tier. It returns deterministic name-number analysis and calculated spelling-variant suggestions toward a target number or category — arithmetic suggestions only, with no outcome claims. Combine it with the name endpoint for the comparisons your product presents.
Rollout Planning
Name tools can generate many calls when users compare lists, so cache aggressively and estimate calls per session. Test representative names in Playground, confirm your UI handles optional or plan-gated fields, and store the X-Request-ID for support cases.