AM/FA - Extend End Date

Details

/external/v1/security-admin/extend-end-date

Synopsis

Extend End Date

put

This route is used to update the end date of an offering. 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 by organizations that have at least one of the following roles on this security: ["issuer","service_provider"]. This endpoint can't be invoked if the security is restricted. This endpoint can be called by applications with access to scope "extendOfferingEndDate".

Required scopes
This endpoint requires the following scopes:
  • : extendOfferingEndDate
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Body
transactionDataall ofRequired

This property contains the transactional data information, i.e. which is the security where the end date is being extended

Example: {"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}
endDateone ofRequired

The new date. Must be after end date.

Example: 2024-09-12T00:00:00.000Z
string · date-timeOptional

Date-time string

Example: 2024-09-12T00:00:00.000Z
or
string · dateOptional

Date string

Example: 1980-01-01
or
number · numberOptional

Epoch timestamp (milliseconds)

Example: 1185106460000
Responses
200

Successfully triggered the process to update the end date.The "processId" and "orchestrationId" properties can be used on the "Transactions API" to monitor the status of this asynchronous process.

application/json
put
/external/v1/security-admin/extend-end-date

Important Notes

Last updated

Was this helpful?