Create Resources Transfer Request
POST /v1/installations/{installationId}/resource-transfer-requests
Prepares to transfer resources from the current installation to a new one. The target installation to transfer resources to will not be known until the verify & accept steps.
/v1/installations/{installationId}/resource-transfer-requests 1 const response = await fetch ( '/v1/installations/string/resource-transfer-requests' , {
4 'Authorization' : 'Bearer YOUR_ACCESS_TOKEN' ,
5 'Content-Type' : 'application/json' ,
13 const data = await response . json ( ) ;
2 "providerClaimId" : "string"
Copy as Markdown Give feedback Ask AI about this page /v1/installations/{installationId}/resource-transfer-requests 1 const response = await fetch ( '/v1/installations/string/resource-transfer-requests' , {
4 'Authorization' : 'Bearer YOUR_ACCESS_TOKEN' ,
5 'Content-Type' : 'application/json' ,
13 const data = await response . json ( ) ;
2 "providerClaimId" : "string"
Authorization System Authentication
Default authentication mechanism
installationId string Required
X-Vercel-Auth string Optional
The auth style used in the request (system, user, etc)
Idempotency-Key string Optional
A unique key to identify a request across multiple retries
This endpoint expects an object.
resourceIds array Required
The IDs of the resources owned by the source installation that will be transferred to the target installation.
expiresAt number Required
The timestamp in milliseconds when the transfer claim expires. After this time, the transfer cannot be claimed.
Claim created successfully
providerClaimId string Required
The provider-specific claim ID for the resource transfer.
400 Input has failed validation
403 Operation failed because the authentication is not allowed to perform this operation
409 Operation failed because of a conflict with the current state of the resource
422 Operation is well-formed, but cannot be executed due to semantic errors