Reject an incoming transfer (owner/admin)
Declines a pending transfer addressed to the caller's org and marks it rejected; the VM stays with the org that offered it. Returns 204 with no body.
Required permission
Requires the transfer.manage permission. See Permissions for the roles and API key permissions that include it.
Command line
The orl CLI wraps this endpoint:
orl transfers reject <id>apiKeyAuthorizationBearer <token>OpenRelay API key. Send it as Authorization: Bearer or_… (legacy vl_… keys still work).
id*stringRejected
curl -X POST 'https://api.openrelay.inc/v1/transfers/string/reject'Accept an incoming transfer (owner/admin) POST
Moves the offered VM to the caller's org and marks the transfer completed. At least one sshKeyIds entry is required; those keys replace the source org's. The source org's GitHub runner config for the VM is deleted, the LLM keys it holds for the VM are revoked, and any other pending transfer of the VM is cancelled. An expired transfer returns 400. If the VM has since moved to a third org, the transfer is cancelled and the call returns 409. The accepting organization takes the VM on as a new workload: one under review, being verified, or whose available balance is under the minimum answers 403 ACCOUNT_RESTRICTED, ACCOUNT_PENDING_VERIFICATION or INSUFFICIENT_BALANCE. One with no price for the VM's or pod's shape answers 400 INVALID_RESOURCE_SIZE, POD_ADMISSION_FAILED or TIER_NOT_PRICED, and nothing moves. When the sending organization can no longer hand the VM over, the call answers 409 TRANSFER_UNAVAILABLE. When either organization's account changes while the accept runs, it answers 409 TRANSFER_ACCOUNT_CHANGED; try again. When the VM changes while the accept runs, it answers 409 CONFLICT; try again. Each of these leaves the transfer pending, so it can still be rejected, or accepted later.
Overview
GPU virtual machines: create, stop, restart or terminate a VM, manage its disks and SSH keys, and read its live burn rate and runway.