# transfer_workspace

Source: https://modulify.ai/docs/api/workspaces/transfer-workspace

Emails another person an invitation to take over a workspace, which changes hands only once they accept it in the product.

- Title: Transfer a workspace to another person
- Scope: `workspaces:write`
- Access: Destructive
- Endpoint: `POST /v1/transfer_workspace`

This is **Transfer workspace** in the workspace's settings. Only the owner can send it, and never for their default workspace. Modulify emails the address an invitation that stays open for 7 days, and nothing changes until the recipient accepts it themselves, from the emailed link or **Pending invitations** in the product. It cannot be accepted over MCP or the [HTTP API](https://modulify.ai/docs/api). It sends a real email to a real person and starts giving the whole workspace away, so the tool tells the client to confirm the address with you first.

On acceptance the recipient owns the whole workspace with its sites, members and bought domains, and you lose access to it. Any paid subscription on it is canceled, so it lands on the Free plan under its new owner, unless it is on Enterprise. [Transfer a workspace](https://modulify.ai/docs/reference/workspaces#transfer-a-workspace) has everything that changes.

A workspace has one pending transfer at a time. Sending another answers `This workspace already has a pending transfer invite. Cancel it before sending a new one!`, so to offer it to someone else, withdraw the current one with `cancel_workspace_transfer` first. It is refused while a GitHub account is connected to the workspace, with `Disconnect the GitHub accounts connected to this workspace before transferring it!`, and your own address is refused with `You cannot transfer a workspace to yourself!`

An address on a temporary email domain is refused unless it already belongs to a Modulify account, with `We do not allow invites to temporary email domains like this one. If you think this is wrong, please contact support!` See [Temporary email addresses](https://modulify.ai/docs/getting-started/create-an-account#temporary-email-addresses). An address with a `+` before the `@` is refused unless it already belongs to a Modulify account, with `You cannot transfer to an address with a + unless it already has a Modulify account. Please use the address without the + part!` See [Addresses with a plus sign](https://modulify.ai/docs/getting-started/create-an-account#addresses-with-a-plus-sign). An address that is not a valid email is refused with `Invalid email address provided!`, and an address that belongs to a Modulify site with `Email addresses that belong to a Modulify site cannot be invited. Please use a different email!`

The response carries the `inviteId` of the invitation, without its link. `get_workspace_transfer` reads it back.

## Request

Call it with a `POST` to `https://api.modulify.ai/v1/transfer_workspace`, sending the inputs below as a JSON object. The token needs the `workspaces:write` scope.

> **Warning**
>
> This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an [Idempotency-Key](https://modulify.ai/docs/api/idempotency) header whenever you might retry it.

```bash
curl -X POST https://api.modulify.ai/v1/transfer_workspace \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"workspaceId":"WORKSPACE_ID","email":"EMAIL"}'
```

Over MCP, the same method is the [transfer_workspace tool](https://modulify.ai/docs/mcp/workspaces/transfer-workspace).

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `workspaceId` | string | Yes | The workspace to transfer, from `list_workspaces`. |
| `email` | string | Yes | The email address of the person to offer it to. They do not need a Modulify account yet. |

## Response

Every call answers with the [JSON envelope](https://modulify.ai/docs/api/requests-and-responses#the-response) of `success`, `message`, `data`, `code` and `version`. `data` holds the result described above, and on a method that returns a total, `count` carries it. The [response headers](https://modulify.ai/docs/api/requests-and-responses#headers-on-every-method-call) carry the call's `X-Request-Id` and what is left of your per-minute budget in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. [Errors](https://modulify.ai/docs/api/errors) explains every status code a call can answer with.