Accept a project transfer
POST/v1/projects/:project_id/transfer/accept
Makes the caller — the member the transfer names — the project's owner.
Usage up to this moment is settled on the previous owner's credit; from here on the project's usage is billed to the caller, and its runs count against the caller's allowance. The project counts toward the caller's plan limits at once: its active channels and triggers, and on Free the project itself. A transfer the caller's plan cannot hold is refused with 403 plan_limit_reached, and the project's retention window is brought within the caller's plan.
The previous owner stays in the project as an admin. Stops recorded against the project's spend move to the caller. Refused to a connected app.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 502
The completed transfer.
Missing or invalid credentials.
The caller's plan cannot hold the project (plan_limit_reached), a project-scoped credential, or a connected app.
No such project, or no transfer to the caller is pending.
The transfer was withdrawn or changed while it was being accepted (transfer_changed).
The project's usage could not be read to settle it before the transfer (upstream_unavailable); nothing was transferred.