AM - Assign Service Provider to Offering
Asset managers can assign service providers, such as fund administrators, that take part in tasks associated with the lifecycle of an offering.
Details
/external/v1/service-providers/assign
Synopsis
This route is used to assign a service provider to an existing offering (e.g. assigning a fund admin).
This will allow the assigned organization to get basic information regarding the security.
This should only be triggered by the organization that owns the security.
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't be invoked if the security is restricted.
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"}}
The id of the service provider organization. Used to uniquely identify the organization on the ledger
US9QIMA
POST /external/v1/service-providers/assign HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 127
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"orgId": "US9QIMA"
}
{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}
Important Notes
Used by the organization that owns the security.
See Blockchain Transaction Tracking for information on using orchestrationId and processId.
\
Last updated
Was this helpful?