hold

the resource's user should call it if want to occupy the resource. "resource" includes "object" or "tangible".
features:

notification for permission(admin owner all features in the features permissions) change, including object/tangible delete.

notification for object attributes, objectName tags objectType description.

notification for tangible attributes, tangibleName distinction .

[internal] added a new attribute "hold" array in tangible table to store the usage description, containing at least "service"/"user"/"description". it could be used as "reference count".

ref: https://miro.com/app/board/uXjVP29GN4Q=/?moveToWidget=3458764590729490039&cot=14

Request Method
Mutation

Request Parameters

Parameter Name	Required	Type	Explain
appName	yes	string	Service name for the app side.
objectId	no	string	The ID of object. At least one parameter, `objectId` or `tangibleId`, must be passed.
user	yes	string	The name of the user .
tangibleId	no	string	The ID of tangible. At least one parameter, `objectId` or `tangibleId`, must be passed.
callbackUrl	no	string	Callback notification URL.
requestHeader	no	string	Request headers (key1=value1, key2=value2) to be returned during the callback.
features	no	array	Permission/attributes name; if not provided, all permissions and attributes will be monitored. It is the same as the features/attributes field of the object. Support all features in the features permissions. eg. `takelive` `rec` `objectName` `tags` `objectType` `description`
description	no	string	Description of how the object is being used.

Return Value

Parameter Name	Required	Type	Explain
errorCode	yes	string	Error code.
errorInfo	yes	string	Error message.

Request Example

Response Example

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Request

Responses