Numerology Learning Guide

What is a Numerology API?

A Numerology API turns a name and date of birth into structured numbers — life path, expression, and more — as JSON, so applications can build numerology features without implementing the calculations themselves.

For developers and product teams Core profile Updated July 8, 2026

The Short Version

The DevDarsha Numerology API converts a name and date into developer-friendly JSON. The entry point is the core profile endpoint, which returns date numbers and name numbers in one call. Requests are authenticated with an API key and use URI versioning under /v1/....

Start with the core profile: it exercises name normalization, date parsing, system selection, and the response envelope together, so it is the fastest way to see the whole shape.

What this guide is for

This is a learning guide, not the API reference. Use it to understand the request and response shape, then use Documentation for exact fields, schemas, and errors.

Systems and Input

Numerology depends on which tradition you use, so the system is an explicit input. Western letter systems (Pythagorean and Chaldean) map a name to numbers; the Vedic Ank Jyotish layer derives date numbers such as moolank and bhagyank. A core request sends a name, a date, and the system you want:

{
  "name": "Aarav Sharma",
  "date": "1990-08-15",
  "system": "pythagorean"
}

Throughout the Numerology guides, examples use Aarav Sharma, born 1990-08-15. Swap the name, date, and system to match your use case.

How to Call the Core Endpoint

Keep your API key on the server and send it in the x-api-key header:

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"}'

Response Envelope

Responses use a consistent envelope with data, meta, and dev_notes. The data object holds the numbers, grouped so you can see which come from the date and which from the name:

  • data.date_numbers: values such as moolank, bhagyank, and life_path_number.
  • Name-based numbers: reported with the system that produced them, for example Pythagorean or Chaldean.
  • meta: the system applied, the API version, and the computation time.

Live Endpoints

The full Numerology surface is live: the core profile, name numbers, personal cycles, compatibility, the Lo Shu grid, a structured JSON report, name-correction suggestions, and bulk processing. Access is plan-gated — the core profile is free, name/cycles/report open on Starter, the Lo Shu grid on Plus, compatibility and name-correction on Pro, and bulk on Scale — so design against the tier your product needs and handle plan-gated fields gracefully.

Recommended Developer Flow

Start with the core profile in Playground to inspect a real response. Decide which system your product presents, and pass it on every call. Then add name numbers or compatibility as needed, cache profiles against their input, and make sure your UI handles optional or plan-gated fields gracefully before launch.

Back to Guides Open Documentation View Pricing Try Playground