Skip to main content
Planning endpoint

Import Plan

POST/schedule-plans/import/

Request body

application/json

See the request guidance below for a valid body.

Handler-checked behavior​

Send a JSON object with a complete plan. Use a unique plan id, unique assignment IDs with matching planId values, and unique lifecycle action IDs with matching schedulePlanId and dependsOn references. Its workflow version, execution scope, topology, and resources must already exist. The server sets source to imported, checks the schedule against those saved records, and returns 422 if it is invalid. It saves the supplied predicted metrics without recalculating them. See the saved-plan import example; a body filled with placeholder IDs would not pass validation.

See the Planning guide for related tasks and context.