TA - Accept Assignment to Offering

Once a service provider, such as a transfer agent accepts assignment to an offering, they can take part in certain tasks associated with the lifecycle of that offering.

Details

/external/v1/service-providers/accept

Synopsis

Accept Assignment to Offering

put

This route is used by a service provider (e.g. Fund Admin) to accept 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 "reject" endpoint has been called. It triggers an asynchronous process that will persist this information on the blockchain, which can be monitored using the "Transactions API" endpoints, after which a background job will be triggered so that this organization can catch up to all the data related to this security (investors, accounts, assets, tender offers, capital events, ...). This endpoint can be called by applications with access to scope "manageServiceProviders".

Required scopes

This endpoint requires the following scopes:

• : manageServiceProviders

Authorizations

oauth2

OAuth2clientCredentialsRequired

Token URL:

Body

application/json

Responses

200

Successfully triggered the acceptance

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

400

The following error codes can be returned: - GN0002 - IS0008 - IS0106 Please refer to the error code dictionary for the details of each error code.

application/json

401

The following error codes can be returned: - AU0001 - AU0003 Please refer to the error code dictionary for the details of each error code.

application/json

403

The following error codes can be returned: - AU0002 - OG0028 Please refer to the error code dictionary for the details of each error code.

application/json

404

The following error codes can be returned: - IS0009 - OG0001 Please refer to the error code dictionary for the details of each error code.

application/json

409

The following error codes can be returned: - IS0119 - IS0013 - IS0010 - IS0102 - IS0103 - IS0117 - SP0001 - SP0006 Please refer to the error code dictionary for the details of each error code.

application/json

put

/external/v1/service-providers/accept

HTTPcURLJavaScriptPython

PUT /external/v1/service-providers/accept HTTP/1.1
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 109

{
  "transactionData": {
    "securityId": "USS3JKS01I00",
    "signer": {
      "email": "[email protected]",
      "name": "John Doe"
    }
  }
}

{
  "processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
  "orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}

Important Notes

• See Blockchain Transaction Tracking for information on using orchestrationId and processId.

\