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

servicestring
user_idstring

Who receives the units: a banking (or concierge) user id, resolved the way every admin RPC resolves a target. Required — a mint to nobody is a malformed request. Only a person: the company is not a holder (#245), and a reserved allocation is seated by the owners' consilium (ConsiliumService.OpenHolderGrant) or by the fee accrual, never by an operator's mint — so there is deliberately no arm for either.

unitsstring

decimal units, > 0

cost_basisstring

Decimal USDT the holder is deemed to have paid. Empty means units × NAV at the dealing mark — what a subscription for these units would have cost right now. An explicit value may be anything, zero included: a stake in an asset the holder already owned cost them no cash. This is what lands in their position's cost basis, and so what their P&L and management fee are measured from.

idempotency_keystring

required, 1..64 chars, unique per service

Response

Success

idstring
servicestring
holder_kindstring

user | allocation. (The company stake's two historical rows never cross the wire: a lookup that lands on one is refused as a conflict, #245.)

holder_idstring

The banking user id for user; the holding allocation's slug (fee) for allocation. A client must never resolve an allocation holder as a user.

unitsstring

decimal units minted or retired (always positive)

navstring

decimal USDT per unit the issuance was recorded at

cost_basisstring

decimal USDT

statestring

queued until the relay posts the leg, then applied. A client that needs the units to be visible on the ledger polls for applied; a queued row is one the relay has not reached yet (or one it parked — see BalanceService.ListParkedEvents).

sourcestring

Where the units came from — or went: mint (IssueUnits or an executed holder grant — supply grew by units) or retire (RetireUnits — burnt out of the holder's account, supply shrank by units). units is always the magnitude; the source is the direction. Always populated; a row that predates the field reads as mint.

Changes

No recorded changes to this operation across all 1 revision of this API.