# transfer_site

Source: https://modulify.ai/docs/api/sites/transfer-site

Emails another person an invitation to take a site, which moves only once they accept it in the product.

- Title: Transfer a site to another person
- Scope: `sites:delete`
- Access: Destructive
- Endpoint: `POST /v1/transfer_site`

This is **Transfer** on the site's card in the dashboard. Modulify emails the address an invitation that stays open for 7 days, and nothing moves 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). You need the **Transfer projects** permission.

On acceptance the site goes to the workspace they pick with its pages, files, database, environment variables, custom domains, comments and publish history. Its chat history, chat attachments, webhooks, deploy hooks, folder, connectors and skills are cleared, and its email domains and forwarding addresses start over when it lands in another workspace. [What moves with a transfer](https://modulify.ai/docs/projects/transfer-a-project#what-moves-with-a-transfer) has the full list.

One side of the transfer has to be on a paid plan. A site in a workspace on a paid plan can be accepted into any workspace. A site in a workspace on the Free plan can still be offered, but only accepted into a workspace on a paid plan, and the answer's message then ends with `Its workspace is on the Free plan, so they can only accept it into a workspace on a paid plan.`, so the client can tell you. See [Before you begin](https://modulify.ai/docs/projects/transfer-a-project#before-you-begin). It is refused when you already invited the same person for this site, when you invited that person less than 3 minutes ago, and when you sent another invitation less than 1 minute ago while it is still pending. Your own address is refused. It sends a real email to a real person and starts giving the site away, so the tool tells the client to confirm the address with you first.

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 `invitedIds`, `alreadyInvitedIds` and `forbiddenIds`, and the invitation without its link. `get_site_transfer` reads it back, and `cancel_site_transfer` withdraws it. To move a site between your own workspaces, use `move_site_to_workspace`.

## Request

Call it with a `POST` to `https://api.modulify.ai/v1/transfer_site`, sending the inputs below as a JSON object. The token needs the `sites:delete` 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_site \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID","email":"EMAIL"}'
```

Over MCP, the same method is the [transfer_site tool](https://modulify.ai/docs/mcp/sites/transfer-site).

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | Yes | The site to transfer, from `list_sites`. |
| `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.