This is a valid gap in the task creation API — afterbegin/beforeend gives you sibling-level positioning, but if you need to nest a task under a specific parent node programmatically, there's currently no direct way to express that relationship in the request payload.

Granular parent-block targeting (being able to pass a parent task ID so the new task is created as a child of that specific node) is something we want to add to the API. This matters a lot for automation workflows that build hierarchical task trees dynamically.

While this specific parameter isn't available yet, you can work around it today by creating the parent task first, capturing its ID from the response, then using a separate API call to create child tasks scoped to that parent context. It's not as clean as a single call, but it gives you the nesting behavior you need.

Full parent-targeting in a single create call is on our API roadmap. Keep an eye on https://taskade.com/changelog for updates, and thank you for the detailed code example — it helps our API team understand the exact gap!

This is in development and your votes helped us prioritize it.

Follow our progress: Changelog | Product Updates

Thanks for your patience and for helping shape Taskade!