FA - Reject Assignment to Offering
A service provider, such as a fund administrator, can decline a role for an offering by rejecting the assignment.
Details
/external/v1/service-providers/reject
Synopsis
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".
This property contains the transactional data information, i.e. which is the security being affected by this action
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}
Successfully triggered the rejection
The following error codes can be returned:
- GN0002
Please refer to the error code dictionary for the details of each error code.
The following error codes can be returned:
-
AU0001
-
AU0003
Please refer to the error code dictionary for the details of each error code.
The following error codes can be returned:
- AU0002
Please refer to the error code dictionary for the details of each error code.
The following error codes can be returned:
-
IS0009
-
OG0001
Please refer to the error code dictionary for the details of each error code.
The following error codes can be returned:
-
IS0013
-
IS0010
-
IS0102
-
IS0103
-
IS0117
-
SP0001
Please refer to the error code dictionary for the details of each error code.
PUT /external/v1/service-providers/reject HTTP/1.1
Host:
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.
\
Last updated
Was this helpful?