Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Outdated release! Latest docs are Release 8.2: API People AssetTransfer v4


For the latest updates on available API endpoints and documentation, see

This is the latest version of the APIs.


Transfers all of the assets owned by one user to another. 

NOTE: The asset transfer endpoint cannot be applied to deleted users. If you are deleting a user, you must transfer the assets first. Then, you can delete the user. This endpoint does not delete users.

NOTE: No checks are made regarding access to the transferred objects for the receiving user. It is possible to transfer ownership of assets that the receiving user cannot access.

NOTE: Shared assets are not transferred.

NOTE: This transfer cannot be undone. You can transfer the receiving user's assets back to the target user, but that step transfers all assets.

Version: v4

Required Permissions

The authenticated user must be an admin.

NOTE: Each request to the Trifacta® platform must include authentication credentials. See API Authentication.


Request Type: PATCH




<tid>Internal identifier of the targeted user to receive the transferred assets.
<id>Internal identifier of the user whose assets are to be transferred.

Request URI - Example:


Request Body:



Response Status Code - Success:  201 - Created

Response Body Example:

                    "connectionId": 7,
                    "personId": 4,
                    "role": "owner",
                    "createdAt": "2019-02-21T19:52:22.993Z",
                    "updatedAt": "2019-02-21T19:52:22.993Z"


connectionIdInternal identifier of the connection to use
personIdInternal identifier of the person receiving the assets.
createdAtTimestamp for when the transfer created
updatedAtTimestamp for when the transfer was last modified

  • No labels

This page has no comments.