Skip to content
Docs

basemodo transfers accept

Accept a Transfer: the App becomes yours, or your Workspace's, at the same URL.

Terminal window
basemodo transfers accept [OPTIONS] <ID>

As an Admin of the Workspace it moves into, or as the Person it is given to. Its Editors stay its Editors but those named by --remove-editor, who no longer reach it: whoever gave it keeps no way in through an Editor they invited. Into a Workspace that pays for no room for it, an Admin approves the charge on basemodo.com first.

Arguments

  • ID (required): The Transfer's id, as basemodo transfers list shows it.
  • --remove-editor <EMAIL> (repeatable): An Editor of the App, by email, to take off it as you accept it (as many times as there are).
  • --approval <ID>: The Charge Approval an Admin approves on basemodo.com, as a refused accept names it.

Like every command, it also takes the global options --json and --api-url.

Examples

Accept a Transfer, its Editors kept:

Terminal window
basemodo transfers accept 6a0c1d2e-3f40-4a5b-8c6d-7e8f9a0b1c2d

Accept it without one of its Editors:

Terminal window
basemodo transfers accept 6a0c1d2e-3f40-4a5b-8c6d-7e8f9a0b1c2d --remove-editor eve@example.com

Output

With --json, it prints the Transfer, {"id", "app", "app_name", "from", "to", "status" (accepted or declined), "requested_at", "decided_at"}. An email that is not one of the App's Editors is an error with code not_an_editor.

From an agent

Basemodo's MCP serves it as the tool transfers_accept. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: id (text), remove_editors (list of text), approval (text). It answers what the command prints with --json.