/v1/muhurta/naamkaran

Baby-naming muhurta.

What this tells you

Scores one proposed naming-ceremony (Naamkaran) date and time. It checks that the ceremony is at least 10 days after birth, the Moon nakshatra, Rahu Kaal and the weekday, and returns a 0–100 score with a grade. It does not suggest name syllables.

Params: date, time, tz, lat, lon and birth_date (YYYY-MM-DD, required), plus optional ayanamsa.

Request

All requests require an Authorization header with your dv_live_* API key.

example request

curl "https://api.lifeastroapi.com/v1/muhurta/naamkaran?date=2027-01-15&tz=Asia%2FKolkata&lat=28.6139&lon=77.209&birth_date=2026-03-01&time=10%3A00" \
  -H "Authorization: Bearer YOUR_API_KEY"

Query parameters

Checked against the API: a parameter is marked required when the request fails without it.

Name	Required	Example	Description
`date`	yes	`2027-01-15`	Date (YYYY-MM-DD).
`tz`	yes	`Asia/Kolkata`	Timezone: IANA name (Asia/Kolkata) or UTC offset (+05:30).
`lat`	yes	`28.6139`	Latitude in decimal degrees.
`lon`	yes	`77.209`	Longitude in decimal degrees.
`birth_date`	yes	`2026-03-01`	Child's birth date (YYYY-MM-DD). Minimum 10 days before ceremony.
`time`	no	`10:00`	Local time (HH:MM, 24-hour). Defaults to 12:00.
`ayanamsa`	no	—	Ayanamsa (sidereal offset) to use. Defaults to lahiri.

Response (200 OK)

The real response to the example request above, generated from the API itself. Long arrays are trimmed to their first two items. Field names are stable across versions.

200 response

{
  "date": "2027-01-15",
  "time": "10:00",
  "birth_date": "2026-03-01",
  "lat": 28.6139,
  "lon": 77.209,
  "ayanamsa": "lahiri",
  "days_since_birth": 320.1875,
  "result": {
    "score": 100,
    "grade": "excellent",
    "factors": [
      {
        "name": "DaysAfterBirth",
        "value": "320 days",
        "weight": 20,
        "score": 20,
        "ok": true
      },
      {
        "name": "Nakshatra",
        "value": "Revati",
        "weight": 20,
        "score": 20,
        "ok": true
      }
    ],
    "warnings": null,
    "is_acceptable": true
  }
}

Field reference

Every field in the response, with its type, a real example, and what it means.

Field	Type	Meaning
date, time	string	Local date and time of the proposed ceremony, echoed from `date` and `time` (time defaults to 12:00). example: `"2027-01-15", "10:00"`
birth_date	string	Baby's birth date, echoed from `birth_date`. example: `"2026-03-01"`
lat, lon	number	Location, used for sunrise, sunset and Rahu Kaal. example: `28.6139, 77.209`
ayanamsa	string	Ayanamsa used for the Moon nakshatra. example: `"lahiri"`
days_since_birth	number	Days from birth_date 00:00 UTC to the ceremony moment. example: `320.1875`
result.score	integer (0–100)	Points earned × 100 / total weight, rounded down. example: `100`
result.grade	string	excellent (90+), good (80–89), acceptable (60–79), inauspicious (below 60). example: `"excellent"`
result.is_acceptable	boolean	True when score is 60 or more. example: `true`
result.factors[]	array	The 4 factors checked: DaysAfterBirth, Nakshatra, RahuKaal, Vara. example: `[…]`
result.factors[].name	string	Factor name. example: `"DaysAfterBirth"`
result.factors[].value	string	Value at the scored moment (day count, nakshatra or weekday). Left out for RahuKaal. example: `"320 days"`
result.factors[].weight	integer	Maximum points for the factor: DaysAfterBirth 20, Nakshatra 20, RahuKaal 15, Vara 10 (65 in total). example: `20`
result.factors[].score	integer	Points earned, from 0 to weight. A nakshatra outside the list earns 8 of 20. example: `20`
result.factors[].ok	boolean	True when the factor is auspicious. DaysAfterBirth is true from 10 days after birth. example: `true`
result.warnings	string[] \| null	Problems found, as plain sentences. null when there are none. example: `null`

Usage tips

How to use it

Ten-day rule
If the ceremony is less than 10 days after birth, DaysAfterBirth earns 0 points and a warning is added.
Scan a date range
To find the best slots in a range, call /v1/muhurta/best-time with purpose=naamkaran and birth_date.

Errors

Every error follows the same envelope. Use the error.code field (not the message) for conditional logic in your integration.

401 Unauthorized

{
  "error": {
    "code": "unauthorized",
    "message": "missing or invalid API key",
    "request_id": "req_01hqy7k8c3e7m1n"
  }
}

402 Payment Required

{
  "error": {
    "code": "trial_exhausted",
    "message": "your free trial credits are exhausted — pick a plan to continue",
    "top_up_url": "https://lifeastroapi.com/pricing",
    "request_id": "req_01hqy7k8c3e7m1n"
  }
}

429 Too Many Requests

{
  "error": {
    "code": "rate_limited",
    "message": "rate limit exceeded; retry after 12 seconds",
    "request_id": "req_01hqy7k8c3e7m1n"
  }
}

Try it

Get a dv_live_* key from your dashboard and paste into the cURL snippet above. New accounts get 1,500 free credits. Sign up.