Generate baby names or child timing

Single endpoint for both flows. Requires a spouse (Wife/Husband) in the family list.

If baby_birth_date is provided → NAMING flow: computes the baby's nakshatra and suggests 12 names with the correct starting syllable.

If omitted → TIMING flow: predicts auspicious child-birth windows from the parent's chart.

Runs in the background - you will be notified when ready.

Request: Bearer token. Requires a spouse (Wife/Husband) in the family list for both flows.

Body:

Naming: baby_birth_date (required to trigger naming) + optional baby_birth_time, baby_birth_place, baby_birth_latitude, baby_birth_longitude, baby_birth_timezone, baby_gender (M/F).

Timing: send an empty body {} (no baby_birth_date).

Success: 200 - returns request_key (Baby-XXXXX), request_type (naming | timing, echoing which flow ran), and a message. Poll GET /child/result/{request_key}.

Errors:

401 - invalid/expired token

409 - a child report of the same type is already pending/processing

422 - no spouse in the family list (add Wife/Husband first)

Request

Body Params application/jsonRequired

Example

{
    "baby_birth_date": "2026-03-15",
    "baby_birth_latitude": 19.076,
    "baby_birth_longitude": 72.8777,
    "baby_birth_place": "Mumbai, India",
    "baby_birth_time": "08:30",
    "baby_birth_timezone": "Asia/Kolkata",
    "baby_gender": "M"
}

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢200OK

application/json

Successful Response

Bodyapplication/json

Examples

Naming flow startedTiming flow started

{
    "success": true,
    "message": "Success",
    "data": {
        "request_key": "Baby-12345",
        "request_type": "naming",
        "message": "Report generation started.\n                                        You will be notified when ready."
    }
}

🟠401Unauthorized

🟠404Record Not Found

🟠409

🟠422Parameter Error