Inv - Create Asset (Lot)

The Integration API refers to the initial step in subscribing as "creating an asset." Throughout the API flows, an asset represents multiple shares, or a lot, of a given security.

Details

/external/v1/primary/assetarrow-up-right

Synopsis

Create Digital Asset

post

This route is used to trigger the recording of a digital asset on the blockchain for a particular security. It is the first action that should be triggered to start the subscription flow. This triggers an asynchronous process (the id of which is returned on the success response) which can be monitored using the "Transactions API" endpoints. This asynchronous process will either be composed of 2 transactions - if the intention is bringing a new investor/account to the ledger, or updating an existing one - or just 1 transaction if this is a subsequent investment done from an existing investor/account without any change. This endpoint can be invoked if the security is in one of the following statuses: ["active"]. This endpoint can be invoked by organizations that have at least one of the following roles on this security: ["investor"]. This endpoint can't be invoked if the security is restricted. This endpoint can be called by applications with access to scope "createSubscription".

chevron-right
lockRequired scopes
This endpoint requires the following scopes:
  • : createSubscription
Authorizations
OAuth2clientCredentialsRequired
Token URL:
Body
bypassFileDataValidationbooleanOptional

Set this to true if you want to bypass file data consistency (e.g. W9 data matching the investor/account information being provided)

Example: true
dryRunbooleanOptional

Set this to true if you want the request to go through the typical request validation stages up until persisting objects to database. If this is set to true then no data will actually be persisted neither on the database nor the blockchain, and no data will be sent out to the issuer, but all the request validations will be executed. A typical use case for this would be for an advisor to check that a subscription being created for a particular client is valid prior to actually sending it out.

Default: falseExample: true
Responses
post
/external/v1/primary/asset

Important Notes

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

  • Use the dryRun option to check the submission for completeness and correctness without persisting the information.

Last updated

Was this helpful?