Request:
mutation {
issueDistributions (
input: {
distributionIds: [
"8f444de2-bfd9-4ca5-b6f4-74c4e511cebc"
]
}
) {
issuanceEvents {
holdingId
}
}
}
Response:
{
"data": {
"issueDistributions": {
"issuanceEvents": [
{
"holdingId": "67ebd6a5-3ffa-4336-b683-31d1d4251a2c"
}
]
}
}
}
In order to maintain backward compatability with the previous method of issuing distributions, the issueDistributions mutation will remain in place for a period of time to be determined. This mutation will eventually be fully deprecated, and those currently using it will have to migrate to the new method described in the section Request Distribution Issuance under Issuer Actions » Primary Issuance. Please speak to your Customer Success representative for further details.
IMPORTANT: If you are new user of the Vertalo API, do not use this mutation as you will not be notified of its deprecation, and your implementation will break.*
In this example, the mutation formally issues shares to an investor based on a distribution ID to create a holding. This transition from distribution to holding effectively locks the shares and binds them to the investor. The ID of the newly created holding is returned in the payload. Note that the distribution ID returned from the previous example of the creation of a distribution is used in the creation of the holding.
Important! Only distributions that are closed may be converted to holdings.
Viewing Issuances
You have the ability to query previous issuances through the API:
query {
allIssuanceEvents {
nodes {
investorId
distributionId
holdingId
createdOn
}
}
}
As with other queries, you may filter on any supported field:
query {
allIssuanceEvents (condition: {investorId: "d6fb328d-2426-4689-98d0-8a0a03679a03"}) {
nodes {
distributionId
holdingId
createdOn
}
}
}