Generate child report (baby names + birth timing)

Starts ONE combined report that always produces both baby name suggestions and child-birth timing. The result is rendered as two tabs on the frontend. Generation runs in the background - you will be notified when ready.

Request: Bearer token | application/json

Partner resolution (the report needs a spouse)

Provide the partner in one of three ways (checked in this order):

family_key - reuse an existing family member as the partner.

partner_name + partner_dob (+ optional partner_birth_time, partner_birth_place, partner_latitude, partner_longitude, partner_timezone) - the partner is added to the family as Wife (user is M) / Husband (user is F) and their kundali is generated.

Nothing - the existing spouse already in the family list is auto-detected.

Baby details (all-or-nothing) → picks Case A vs Case B

Case A - send baby_birth_date and all of baby_birth_time, baby_birth_place, baby_birth_latitude, baby_birth_longitude, baby_birth_timezone, baby_gender. Names come from the baby's nakshatra; since the baby is already born, the timing tab gives a warm, positive reading of the birth moment (blessings and strengths of the chart, never a good/bad verdict); the baby is added to the family list as Son/Daughter with its own kundali.

Case B - send no baby_* fields. The timing tab predicts auspicious birth windows from both parents' charts, and names are generated from both parents' nakshatras.

Sending baby_birth_date without the other baby fields → 422.

One report per user

Only one child report can exist at a time. To generate a new one, remove the spouse from the family list (which soft-deletes the existing report).

Success: 200 - returns request_key (Baby-XXXXX) and a message. Poll GET /child/result/{request_key}. Also returns 200 with success: false and code: PLAN_LIMIT (not an HTTP error) when header X-Enforce-Paywall: true is sent and no unconsumed child-report purchase credit exists for this partner (get one via POST /subscriptions/checkout with slug child-name-timing first - checkout never generates the report itself, this endpoint is always the separate step-2 call, paid or free-via-coupon). If a purchase is still pending (paid moments ago, webhook not yet processed), this call reconciles it against Razorpay live before deciding - if confirmed paid the credit activates and generation proceeds normally; if not, the message is "We're still verifying your payment..." instead of the plain "this report needs to be purchased" text shown when no attempt exists at all

Retry after a failed report (2026-08-20): unlike palm/marriage, a failed child report still blocks (409) - the only recovery path is removing the spouse from the family list (soft-deletes the report) and re-adding them, then calling this endpoint again. As of 2026-08-20 that regenerate DOES reuse the original already-paid credit automatically - a credit only counts as spent once a report actually reaches done, so removing/re-adding the spouse after a failure no longer requires a fresh purchase. It's always safe to call POST /subscriptions/checkout (slug child-name-timing) again first too - it will report requires_payment: false and hand back the same purchase.

Errors:

401 - invalid/expired token

404 - family_key does not match a family member of this user

409 - a child report already exists (remove the spouse to regenerate)

422 - no spouse available (none in family and no partner details), inline partner details sent while a spouse already exists, or partial baby details

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Body Params application/jsonRequired

Examples

Case A - existing spouse + baby detailsCase B - new partner inline, no baby detailsCase B/C - spouse already in family (empty body)

{
    "family_key": "Family-12345",
    "baby_birth_date": "2026-03-15",
    "baby_birth_time": "08:30",
    "baby_birth_place": "Mumbai, India",
    "baby_birth_latitude": 19.076,
    "baby_birth_longitude": 72.8777,
    "baby_birth_timezone": "UTC+5.5",
    "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

Example

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

🟠401Unauthorized

🟠404Record Not Found

🟠409Record Not Found

🟠422Parameter Error