Pending incoming transfers (enriched)
The pending transfers addressed to the org, newest first, each with the VM's name (Deleted VM once it is gone) and the sending org's name and slug. A transfer past its 7-day expiry stays listed as pending until it is rejected or cancelled, or an accept attempt marks it expired.
Required permission
Requires the transfer.read permission. See Permissions for the roles and API key permissions that include it.
Command line
The orl CLI wraps this endpoint:
orl transfers incoming listapiKeyAuthorizationBearer <token>OpenRelay API key. Send it as Authorization: Bearer or_… (legacy vl_… keys still work).
orgId*stringOK
application/json- response
[index: integer]?curl -X GET 'https://api.openrelay.inc/v1/orgs/string/transfers/incoming'[ { "id": "string", "resourceType": "string", "vmId": "string", "status": "string", "note": "string", "createdAt": "string", "expiresAt": "string", "respondedAt": "string", "completedAt": "string", "resourceName": "string", "sourceOrgName": "string", "sourceOrgSlug": "string", "targetOrgName": "string", "targetOrgSlug": "string" }]Start a resource transfer (owner/admin) POST
Offers one of the org's VMs to another organization, named by targetOrgSlug, and returns the pending transfer, which can be accepted for 7 days. A VM can have one unexpired pending transfer at a time; a second returns 409, as does an inference serving replica. Naming the caller's own org returns 400. An organization under review or being verified cannot offer a VM: the offer answers 403 ACCOUNT_RESTRICTED or ACCOUNT_PENDING_VERIFICATION.
Outgoing transfers, all statuses (enriched) GET
The transfers the org has sent, in every status, newest first and at most 50, each with the VM's name and the receiving org's name and slug.