Neon API (unofficial showcase)
POST/users/me/projects/transferDeprecated

Transfer projects from personal account to organization

Deprecated. Personal accounts have been migrated to organizations, so this operation no longer applies. Removal scheduled for July 1, 2026.

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

2 body fields
destination_org_idstringrequired
The destination organization identifier
project_idsarray<string>required
The list of projects ids to transfer. Maximum of 400 project ids

4 status codes
200Projects successfully transferred from personal account to organization
406Transfer failed. The target organization has too many projects or an incompatible plan. Reduce projects or upgrade the target organization.
limitsarray<object>required
Plan limits that were not satisfied by the request.
422Transfer failed. Projects with active integrations (for example, GitHub or Vercel) cannot be transferred.
projectsarray<object>required
Projects that have the requested integration, each including the project details and associated integration metadata.
defaultGeneral Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress.
request_idstringoptional
Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.
codestringrequired
Machine-readable code classifying the error type. See `message` for a human-readable explanation.
Default:
messagestringrequired
Error message

Error handling

A 406 is returned: Transfer failed. The target organization has too many projects or an incompatible plan. Reduce projects or upgrade the target organization. A 422 is returned: Transfer failed. Projects with active integrations (for example, GitHub or Vercel) cannot be transferred. Any other status is an error: General Error.

The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received.

  • If no response is returned from the API, a network error or timeout likely occurred.
  • In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results.

The following HTTP methods are considered non-idempotent: POST, PATCH, DELETE, and PUT. Retrying these methods is generally not safe. The following methods are considered idempotent: GET, HEAD, and OPTIONS. Retrying these methods is safe in the event of a network error or timeout.

Any request that returns a 503 Service Unavailable response is always safe to retry.

Any request that returns a 423 Locked response is safe to retry. 423 Locked indicates that the resource is temporarily locked, for example, due to another operation in progress.