Make a GET request
GET https://babydayplan.com/api/v1/schedule?age_days=180&wake=07:00&naps=auto&feeding=breast&dream=0| Parameter | Allowed values |
|---|---|
| age_days | Required integer, 0–1080 |
| wake | HH:MM, 04:00–10:00; default 07:00 |
| naps | auto (default), or 0–7 within the selected age’s supported band |
| feeding | breast (default), formula or mixed |
| dream | 0 (default) or 1, through age_days=180 only |
What comes back
The result contains contiguous 24-hour segments, local clock labels, feed markers, source-bearing age/feeding guidance, assumptions and a share path. typical_not_prescriptive is always true. Sleep opportunity is not guaranteed sleep and night rest includes breaks.
{
"age_days": 180,
"nap_count": 3,
"bedtime": "8:00 pm",
"sleep_opportunity_minutes": 840,
"share_path": "/schedule/?age_days=180&wake=07%3A00&naps=auto&feeding=breast&dream=0",
"typical_not_prescriptive": true,
"note": "Rest blocks show sleep opportunities, not guaranteed sleep. Feeding and comfort interrupt rest; always follow hunger cues and the pediatrician."
}Limits and errors
60 requests per minute per salted network hash. Over-limit requests return 429 with Retry-After. Invalid, array or extra inputs return 422; unsupported HTTP methods return 405. Do not send names, birth dates or medical records.
Reuse with context
Keep the typical-example, feeding and safe-sleep labels, and link to the methodology and actual sources. The embed guide gives a readable widget.
A few little questions.
Is the API personalized medical advice?
It generates an educational example from age and schedule choices; it does not assess a child.
Are schedules stored?
The application computes them from the request. URLs may still appear in browser history and hosting access logs.
Why can a nap option return an error?
It must fit both the source-based age band and the model’s selected wake intervals. There is no silent constraint relaxation.
Can the disclaimer be removed?
Keep all typical-example and safety context when reusing a result.