templates
Confirm Integration Shape
Mark integration_shape as confirmed. Only after this does the MCP's coverage-gap checks escalate to HIGH severity — before confirmation, the loop is about negotiating the shape itself.
The coding agent should only call this once it has verified the shape matches the actual codebase (endpoints exist, frontend callbacks are wired, chained flows have real dependencies).
post/v1/templates/{template_id}/integration-shape/confirm
Path parameters
template_idstring required
Response
Successful Response
{"stackTrail":"paths:/v1/templates/{template_id}/integration-shape/confirm:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}
Changes
No recorded changes to this endpoint across all 1 revision of this API.