Transfer User Content

post https://api.lucid.co/transferUserContent

Transfers ownership of Lucid documents and objects from one user to another.

Note that both the fromUser and toUser must be on the same account as the admin authorizing the transfer.
This endpoint transfers the following to the toUser:
- Documents and folders owned by the fromUser. The toUser will also be given edit and share permissions to any team folder the fromUser has edit and share permissions for.
- Custom shape libraries
- Lucidscale objects (3rd party credentials, AWS accounts, Google Cloud projects, and Azure subscriptions)
After the transfer, the fromUser loses ownership of the objects described above. An email is also sent to both the fromUser and the toUser to notify them of the transfer.

📘
Note: Use of this endpoint can only be authorized by administrators on accounts with Enterprise licenses.
Note: This endpoint has a per account rate limit of 30 requests per 5 seconds.

📘
This endpoint does not delete or delicense the fromUser.

Valid Authentication Methods

OAuth 2.0 Account Token Scopes:

account.user.transfercontent

Responses

204

No Content when ownership is successfully transferred.

400

Bad Request when the fromUser and toUser are the same.

403

Forbidden when the users do not exist or are not on the authenticated account.

429

Too Many Requests if the account makes more than 30 requests in 5 seconds.

Language

Credentials

OAuth2


xxxxxxxxxx
1
curl --request POST \
2
     --url https://api.lucid.co/transferUserContent \
3
     --header 'Lucid-Api-Version: 1' \
4
     --header 'content-type: application/json'

Click Try It! to start a request and see the response here!