REST API Reference

Back Next

Changing the owner of a file listener association

A file listener can be associated with a taskflow or with file ingestion tasks. You can use file listener as a source or schedule (trigger) for file ingestion tasks and as a trigger for a taskflow. A file listener association is the internal link between file listener and its associated file ingestion tasks or taskflows. The owner of a file listener association is the last person who selected the file listener as a source or schedule in a file ingestion task or the last person who published the taskflow with the file listener as a trigger.

You might want to change or transfer the owner of a file listener association when a user who owns the file listener association leaves the organization. For example, if the user Alex creates a file ingestion task, the user Beth creates a file listener, and the user Clara selects the file listener as a source or schedule in a file ingestion task, Clara is the owner of the file listener association. If Clara leaves the organization, you must reassign her assigned file listener associations to another user before you can delete her user account.

POST request

Use a POST request to change the owner of a file listener association from one user to an another.

Use the following URI to change the owner of a file listener association:

POST <serverUrl>/mftsaas/api/v1/ChangeCallbackOwnership

Use the following fields in the POST request:

Field	Type	Required	Description
currentOwner	String	Yes	User ID of the current owner.
newOwner	String	Yes	User ID of the new owner.

POST request example

Use this sample as a reference to change the owner of a file listener association.

POST <serverUrl>/mftsaas/api/v1/ChangeCallbackOwnership
Content-Type: application/json
Accept:application/json
Content-Type:application/json
IDS-SESSION-ID:{{IDS-SESSION-ID}}
{
    "currentOwner": "{{UserIDwhoLeftTheOrganization}}",
    "newOwner": "{{NewUserID}}"
}