banking.v1.AllocationsService
Mint units to a holder with no cash leg (AllocationManage). The allocation must be registered, in any state — a product is normally seeded before it opens. The mint is priced at the current (fresh) NAV for the record and the holder's cost basis, and counts against the unit cap exactly as a subscription does: an operator sizing a product below what they mean to issue raises the cap first, then issues.
Idempotent by idempotency_key, unique per service: a retry of a timed-out call returns the issuance the key already names and mints nothing. A key reused for a DIFFERENT holder or amount is ALREADY_EXISTS — the retry is the case the key exists for, the reuse is the mistake it has to catch.
post/banking.v1.AllocationsService/IssueUnits
Request
- The document declares no server URL.
- Auth: none required
Headers
Connect-Protocol-Version1 required
Define the version of the Connect protocol
Connect-Timeout-Msnumber
Define the timeout, in ms
Request body
Response
Success
Changes
No recorded changes to this operation across all 1 revision of this API.