Skip to main content
POST
Transfer a client
Emails your client a link from your name. Once they accept it, signed in to their own Orgo account (or a new one), the workspace, its computers, and its key are theirs, on their plan and AI credits. Whatever you built on the key keeps working. You stay on as an admin until they remove you, and any billing through you ends. The link works for 14 days. Sending again replaces it. If their plan can’t run the computers yet, they pick one before accepting. Use your account-wide API key. A client’s own key gets 403 here. See Invoicing.

Path parameters

string
required
The client’s id.

Body

string
required
Your client’s email. They accept signed in with it.

Response

The client, with transfer set. After they accept, its status is transferred.

Example

Response

Errors

Authorizations

Authorization
string
header
required

API key authentication. Get your key at orgo.ai/workspaces

Path Parameters

id
string
required

The client’s id.

Body

application/json
email
string
required

Your client’s email. They accept signed in with it.

Response

OK

A client: a workspace you run for them, with a key scoped to it.

id
string
external_id
string
name
string | null
status
enum<string>
Available options:
active,
closed,
transferred
workspace_id
string
created_at
string<date-time>
closed_at
string<date-time> | null
limits
object
usage
object
billing
object | null
transfer
object | null
computers
object[]

On Get client only.