Identifiers - Securitize Developers

Identifier	Shape	What it identifies	Where you find it
`tokenId`	Opaque string	One fund’s token on one chain	`GET /assets`, every deposit, transaction and event
Deposit `id`	Digits, as a string	One cash movement	`GET /deposits`, `investor.deposit.processed` `data.id`, `investor.minting.completed` `depositMovements[].id`
`tokenIssuanceId`	Digits, as a string	One minting of tokens to you	A deposit once tokens are issued for it, an issuance transaction, `investor.minting.completed` `data.id`
Transaction `id`	Digits, as a string	One token transaction	`GET /transactions`, `investor.transaction.processed` `data.id`
`txHash`	`0x` and hex	The transaction on chain	Transactions, `investor.minting.completed`, the redemption events, `sourceTransaction`
Redemption `id`	Opaque string	One redemption, from accepted to paid	`data.id` of `investor.redemption.pending`, `.confirmed`, `investor.payout.initiated`, `.completed`
`uetr`	Opaque string	A bank transfer’s Unique End-to-end Transaction Reference	Deposits paid by wire
`eventId`	`<eventType>-<id>`	One event. The deduplication key	The body of every webhook; `GET /webhook-events/{eventId}`
`svix-id`	`msg_` and 27 characters	One message, the same on every retry of it	The delivery’s header; `id` in `GET /webhook-events`

Ids are strings: compare them as strings, never as numbers, and never rely on their order.

The keys that join the steps

To join	Use	On each side
A deposit to its webhook	Deposit `id`	`GET /deposits` `id` = `investor.deposit.processed` `data.id`
Cash movements to the tokens they bought	`tokenIssuanceId`	Deposit `tokenIssuanceId` = `investor.minting.completed` `data.id`; also `depositMovements[].id` = deposit `id`, for the `deposit` and for its `liquidation`
The tokens to the chain	`tokenIssuanceId`, `txHash`	Transaction `tokenIssuanceId` and `txHash` = the minting’s `data.id` and `txHash`
A redemption transfer to its redemption	`txHash`	Transaction `txHash` = `investor.redemption.pending` `data.txHash` = payout `sourceTransaction.txHash`
The steps of one redemption	Redemption `id`	`data.id` of pending, confirmed, payout initiated and payout completed

One token issuance is behind several cash movements: each deposit that funded it and the liquidation that applied it. A deposit’s tokenIssuanceId is null until tokens are issued for it; a transaction’s is null when it is not an issuance.

Scoping

Every response and every event is scoped to the investor account your credentials belong to:

Lists show your deposits and the transactions you are a party to, only.
An id outside your account answers 404, the same as an id that does not exist: DEPOSIT_NOT_FOUND, TRANSACTION_NOT_FOUND, WEBHOOK_EVENT_NOT_FOUND. A token you have no relationship with answers TOKEN_NOT_FOUND.
Webhooks and GET /webhook-events carry only the events of your account.