Reference / browser control plane / generated
POST
/v1/projects/{projectId}/transferTransfer a personal project to an organization.
Moves the stable project ownership root from the caller's personal account to an organization where they are an owner or admin. Project API keys, provider profiles, sandboxes, and idempotency records remain attached to the unchanged project ID.
Operation ID
transferProjectSuccess200
AuthenticationBrowser session
CSRF headerX-Wildflower-Csrf
Request contract
projectIdis a required path parameter.
The JSON request body uses the TransferProjectInput model.
Same-origin request example
This operator-oriented example makes the cookie and CSRF boundaries explicit. Use an isolated browser test session, keep both values out of shell history, and replace generated path variables before execution.
curl --request POST \ --cookie "wildflower_session=${WILDFLOWER_SESSION}" \ --header "X-Wildflower-Csrf: ${WILDFLOWER_CSRF_TOKEN}" \ --header "Content-Type: application/json" \ --data @request.json \ "https://wildflower.computer/v1/projects/${WILDFLOWER_PROJECT_ID}/transfer"SDK boundary
This operation powers the account console and is not emitted in the TypeScript, Python, Rust, Go, or Zig project-key SDKs. Use the generated public API reference for sandbox automation.
