This article discusses a theoretical method for creating a watch using the pigeon endpoint.
It is highly likely that a CORS policy restriction will be encountered when attempting this and as such this method can not be guaranteed to work nor can it be supported. It is strictly provided on an informational basis.
The Pigeon API is restricted by CORS policy. Therefore, depending on how the call is made, it may not be possible to use the API to create watch requests.
The two pieces of information that will be required ahead of time will be
You must use the UUID; an object ID will not work. The UUID appears as an alphanumeric string like be2943ba-7476-44d9-baea-9b8e1151b708 and is available via a standard WSAPI GET to the appropriate user or artifact object.
The call needs to be constructed as follows:
|UserUUID: <ObjectUUID of user to be added as watcher>,|
|ArtifactUUID: <ObjectUUID of artifact to be watched>|