AM/TA - Cancel Capital Event

You can cancel a capital event before launch.

Details

/external/v1/capital-events/{capitalEventId}/cancelarrow-up-right

Synopsis

Cancel Capital Event

put

This route is used to trigger the cancellation of the capital event (capital call or distribution). This is an irreversible action that can be called if the event is in draft state. The typical use case for this endpoint is to cancel an event that was created by mistake. 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 invoked if the security is in one of the following statuses: ["active","completed","approved_revert_to_active","closed"]. This endpoint can be invoked if the capital event is in one of the following statuses: ["draft"] This endpoint can be invoked by organizations that have at least one of the following roles on this security: ["issuer","service_provider"]. This endpoint can be called by applications with access to scope "manageCapitalEvent".

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
  • : manageCapitalEvent
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Path parameters
capitalEventIdanyRequired

The id that uniquely identifies the capital event on the ledger.

Example: TEST5678
Body
processIdstringOptional

This is an externally provided id that can be used to identify the asynchronous process that will be triggered by this action. It is optional. If not provided the system will generate a unique id for this. If provided, it must have a v4 UUID format.

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

This is the security unique identifier on the ledger. It uniquely identifies a particular security on the blockchain. It is optional. Either "securityId" or "securityCorrelationData" must be provided, but not both.

Example: USS3JKS01I00
Responses
chevron-right
200

Successfully triggered the cancellation of the capital event.The "processId" and "orchestrationId" properties can be used on the "Transactions API" to monitor the status of this asynchronous process.

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/capital-events/{capitalEventId}/cancel

Important Notes

\

Last updated

Was this helpful?