Accept a project transfer request
Accepts a transfer request for the specified project, transferring it to the specified organization
PUT /projects/{project_id}/transfer_requests/{request_id}
Accepts a transfer request for the specified project, transferring it to the specified organization or user. If org_id is not passed, the project will be transferred to the current user or organization account.
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/transfer_requests/$REQUEST_ID" \
-X PUT \
-H "Authorization: Bearer $NEON_API_KEY"Every field below is optional. An empty body works too.
Also available in
import { createNeonClient, raw } from '@neon/sdk';
const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.acceptProjectTransferRequest({
client: neon.client,
path: {
project_id: process.env.PROJECT_ID,
request_id: process.env.REQUEST_ID
}
});Console path: Claim
Parameters
Section titled “Parameters”Project ID
project_id
string
The Neon project ID
Request ID
request_id
string
The Neon project transfer request ID
Request body
Section titled “Request body”No field is required. Send an empty body to use sensible defaults.
Organization
org_id
string
The Neon organization ID to transfer the project to. If not provided, the project will be transferred to the current user or organization account.
Errors
Section titled “Errors”406
Account doesn't satisfy the plan requirements to own the project
default
General error
This endpoint can return the standard Neon API error response.
Response fields
messageRequired. Human-readable error message.codeRequired. Machine-readable error code.request_idOptional. Request identifier for debugging. You can provide one with theX-Request-IDheader.
Retry guidance
If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.
Idempotent methods (GET, HEAD, OPTIONS) are generally safe to retry after a network error or timeout. Non-idempotent methods (POST, PATCH, DELETE, PUT) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.
Responses with 423 Locked or 503 Service Unavailable are safe to retry. 423 Locked means the resource is temporarily locked, usually because another operation is in progress.