TA - Reject Assignment to Offering

A service provider, such as a transfer agent, can decline a role for an offering by rejecting the assignment.

Details

/external/v1/service-providers/rejectarrow-up-right

Synopsis

Reject Assignment to Offering

put

This route is used by a service provider (e.g. Fund Admin) to reject the assignment to an existing offering. This can be invoked if the current organization has been assigned to a particular security. It can also be invoked at any time after the "accept" endpoint has been called. In this case, this will prevent further actions from being executed on this security and this organization will no longer be entitled to receiving new transactions' data. It triggers an asynchronous process that will persist this information on the blockchain, which can be monitored using the "Transactions API" endpoints. This endpoint can be called by applications with access to scope "manageServiceProviders".

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
  • : manageServiceProviders
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Body
Responses
chevron-right
200

Successfully triggered the rejection

application/json
processIdstringRequired

This is used to uniquely identity a transaction process on this system.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf
orchestrationIdstringRequired

The orchestration id. It is used to uniquely identity a group of transactions that are being orchestrated following an action request.If a processId was passed as an input to the action, it will be returned on this property.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf
put
/external/v1/service-providers/reject

Important Notes

\

Last updated

Was this helpful?