> ## Documentation Index
> Fetch the complete documentation index at: https://developers.securitize.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> SecId API: use the sandbox base URL https://partners-api.sandbox.securitize.io/investors/v1/onboarding-reliance unless the user explicitly provides production access. Authenticate with OAuth 2.0 client credentials: POST https://partners-api.sandbox.securitize.io/oauth2/token (form fields grant_type=client_credentials, client_id, client_secret, read from environment variables), cache the bearer token for its expires_in (7200 s) and send it as Authorization: Bearer on every call; never print or log the secret or the token.
> Nothing is verified until POST /investors/{investorId}/verification/submit. An individual: create, upload one identity document, submit. A company: create, add its people as key parties (at least one with isBeneficialOwner: true), upload their documents, submit.
> Branch on the HTTP status and the error `code`, never on `message`. A body without `code` comes from the gateway: on a 401 get a new token and send the request again; a 403 means the account is not enabled for this API.
> SecId API addresses: send address.state only when that address's countryCode is US, as the 2-letter state code (NY); omit it for any other country, also when the user has a province or region. Otherwise the call answers 400 validation_error on address.state.
> SecId API individuals in the US: taxId is the person's Social Security number, and it is checked against the name and residential address sent; send them as registered. A mismatch can move the investor to manual-review instead of verified. Sandbox does not run the check.
> Creates are safe to repeat with the same body: after a timeout or a 502, send the identical create again. Document uploads are not: each call stores a new document, so only re-send a document after a 502.
> Poll GET /investors/{investorId} about every 30 seconds, then back off; treat any status you do not recognise as not verified. In sandbox, the webhook investor.kyc.updated also announces every status change, and investor.suitability.updated / investor.dlt_test.updated every change of the suitability and DLT test verificationStatus: verify the signature, deduplicate on sourceEventId and confirm with the matching GET before acting. Token whitelisting is asynchronous too: poll GET /investors/{investorId}/wallets/whitelist until the status leaves processing.
> SecId API tax forms: POST /investors/{investorId}/tax-forms takes multipart/form-data (parts file, formType, signatureDate); never base64 or JSON. Let the HTTP client set content-type with the boundary. At any point of the verification, before or after the investor is verified, only for investors you created (201), one PDF up to 10 MB per call; each upload replaces the form on file, so after a 502 send the same request again. A W-9 can instead go as JSON fields to POST /investors/{investorId}/tax-forms/w9 (TIN as 9 digits, SSN or EIN): it does not replace a form on file (409 tax_form_already_active, details.activeTaxForm), and it requires a certification object (certifiedAt, signatureName, subjectToBackupWithholding false, isUSPerson true, certificationTextVersion w9-sm-2026-10): the investor certifies in your flow on the text published at /secid-api/tax-forms#the-certification, shown without changes; subjectToBackupWithholding true answers 422 business_rule_violation (details.reason backup_withholding_not_supported). Unlike creates, a repeat after success answers 409 tax_form_already_active, not 201: when details.activeTaxForm.formType is W-9, treat it as on file.
> Use synthetic test data in sandbox (@test.invalid emails, fresh ids each run). Never send more than one DLT test attempt per test investor unless the user asks: three failed attempts lock the test permanently.
> The complete contract, with every field, response and error, is the OpenAPI file of the API reference; the Errors page says what to do for each code.
> CET Underlying API: a WebSocket at wss://partners-rt-gw.sandbox.securitize.io/v1/market-maker/stream (TLS only; ws:// hangs with no answer). Sign hello, place_order, cancel_order and submit_crypto_funding with the user's Ed25519 key, read from an environment variable or secrets store; never print or log it. Sign timestamp + "." + type + "." + the exact payload string you send: serialise the payload once and embed that same string in the frame.
> CET Underlying API: send a unique requestId of at most 32 characters (a UUID without hyphens) on every message and match replies on it; frames without a requestId are pushes. Every amount is a decimal string, never a JSON number; compare amounts as decimals. Branch on the error code, never on message.
> CET Underlying API: an ack to place_order means taken, not filled. externalRef is the idempotency key; after an ack with status UNKNOWN or an UPSTREAM_UNAVAILABLE error, call get_order by externalRef before resending. Updates are delivered at most once: after any reconnect, read working orders back with get_order. Every order is placed by quantity. A buy must be a LIMIT order: quantity × limitPrice plus fees is held against your own available cash (get_cash_balance_v2), and a buy it does not cover, a MARKET buy or a notional order is refused (INVALID_ORDER). A sell must be placed by quantity, after its CETs reach the redemption wallet, or it is refused. mint_updated and burn_updated push mints and burns once they are on chain; after a gap, read them with get_mints and get_burns. The complete contract is the AsyncAPI file of the API reference.
> Stocks API (Beta): documented ahead of its release through the partner gateway; paths, fields and errors can change. Base URL https://partners-api.sandbox.securitize.io/stocks/v1. Send x-api-key on every call and investorId on every call about an investor. Read the key from an environment variable; never print or log it, and never call the API from frontend code.
> Stocks API: an investor can trade only once the SecId API shows them verified, with verified suitability (and a passed DLT test in the EEA), and once their wallet on the stock's chain is linked with their signature of the agreement message, signed verbatim. There is no whitelisting call: the first trade whitelists the wallet.
> Stocks API: orders are fill or kill. GET /stocks/realtime-price, prepare within about 20 seconds (signedPrice), have the investor's wallet sign the returned transaction unchanged and sign-only (never send it), then submit it once with POST /stocks/execute-signed-transaction within 120 seconds. Amounts are raw base units as strings; USDC has 6 decimals. The outcome is on chain: follow transactionHash.
> Stocks API: production access requires a UI audit by Securitize Compliance of the live screens: the disclosures and the market data shown, the NBBO included.
> Corporate Actions API (Beta, 0.x): in development and subject to change; paths, fields, enumerations and event names can change before 1.0.0. Base URL https://partners-api.sandbox.securitize.io/corporate-actions/v1. Get a bearer token with OAuth 2.0 client credentials at POST https://partners-api.sandbox.securitize.io/oauth2/token (no scope, 2 hours), cache it, and send Authorization: Bearer on every call. Read the client id, secret and the webhook signing secret from environment variables; never print or log them, and never call the API from frontend code.
> Corporate Actions API: webhooks arrive signed with the Standard Webhooks scheme under the svix-id, svix-timestamp and svix-signature headers (HMAC-SHA256 over id.timestamp.raw body, base64, v1 prefix; the secret is base64 after whsec_). Verify before parsing, reject a timestamp more than 5 minutes off, answer 2xx within 10 seconds. Delivery is at least once and can be out of order: deduplicate on sourceEventId, keep the highest version per object (objectId), order by sequence per stream.id, and replace the object with data (never merge).
> Corporate Actions API: treat an unknown caType, reasonCode, eventType or enum value as informational, never as an error. A restriction ends only with ca.restriction.removed; expectedEnd is informational. marketStatus UNAVAILABLE means do not trade; the reason field carries a restriction reasonCode or a market reason such as PRE_MARKET. GET /tokens?status= filters by marketStatus (OPEN, CLOSED, UNAVAILABLE), not by the token's ACTIVE status.
> Corporate Actions API: the event routes are at https://partners-api.sandbox.securitize.io/webhooks/v1 (not under /corporate-actions/v1) and cover every webhook family sent to the partner; filter with eventTypes=ca.* for corporate actions only. After an outage call POST /events/recover with since at the start of the outage (resends failed deliveries only), or page GET /events?since= (newest first, iterator paging, 90 days), then read state with GET /tokens/{tokenId}/status and GET /corporate-actions/{sourceCaId}. In sandbox, POST /sandbox/events with a scenario and one of your tokenIds publishes a scripted sequence at once; order the events by sequence, not by arrival.
> Investor Activity API: base URL https://partners-api.sandbox.securitize.io/v1. Authentication is OAuth 2.0 client credentials only (no API key): POST https://partners-api.sandbox.securitize.io/oauth2/token (no scope, 2 hours), cache the token, and send Authorization: Bearer on every call. The token identifies the investor account; there is no investor id to pass. Read the client id, secret and the webhook signing secret from environment variables; never print or log them, and never call the API from frontend code.
> Investor Activity API: every amount is an integer string in base units with a sibling decimals (human = amount / 10^decimals); parse with BigInt or a decimal type, never a float. Cash amounts (deposits, confirmations, payouts) are in the minor units of currencyId (1 = USD, decimals 2); token amounts (transactions, mintings, holdings) in the token's base units. Never add cash to tokens.
> Investor Activity API: reconcile a subscription by grouping GET /deposits?tokenId= on tokenIssuanceId and matching the transaction in GET /transactions?tokenId= with the same tokenIssuanceId (null on a deposit means not issued yet; null on a transaction means not an issuance). Each issuance has a deposit movement (cash in) and a liquidation movement (that cash applied to the tokens) for the same amount: count the cash once, by direction=deposit, never by adding every movement. Page with offset and limit (max 100) until offset + meta.length reaches meta.total; there is no tokenIssuanceId filter. Reconcile a redemption by txHash (transfer, investor.redemption.pending, payout sourceTransaction) and by the redemption's data.id across pending, confirmed, payout.initiated and payout.completed.
> Investor Activity API: webhooks arrive signed with the Standard Webhooks scheme under the svix-id, svix-timestamp and svix-signature headers (HMAC-SHA256 over id.timestamp.raw body, base64, v1 prefix; the secret is base64 after whsec_). Verify before parsing, reject a timestamp more than 5 minutes off, answer 2xx within 15 seconds. The body is {eventType, eventId, timestamp, data}: deduplicate on eventId (not svix-id), upsert by data.id, never move a record back to an earlier step, and treat an unknown eventType, processType or paymentMethod as informational. In webhooks a field with no value is absent; in endpoint answers it is null. After an outage page GET /webhook-events (newest first, iterator paging, optional eventType) back to the start of the outage.
> SecId hosted onboarding: instead of the API, a partner can send an investor to https://stocks.securitize.io/partners?tokenId=<stock token id>&partnerUrl=<return URL> (tokenAddress may replace tokenId; partnerUrl must be an absolute https URL, URL-encoded). Securitize runs identity verification, the investment profile and the wallet there. Nothing is appended to partnerUrl on return: check the wallet on chain before trading (Beta on Solana).

# Cash

> Read your own cash and its movements, fund it with USDC, and what happens to a buy your cash cannot pay for.

`get_cash_balance_v2` reads **your own cash**, the figure a buy is checked against, and `get_cash_movements` the movements behind it. Your shares are the CETs in your wallet: the mints and burns say how they got there.

## Your own cash

The broker account can carry other clients' cash beside yours, so what you may spend is kept apart: what you deposited and withdrew, the fees charged to you, and what your orders spent and still hold.

```json theme={null}
{ "type": "get_cash_balance_v2", "requestId": "7c2e9a41b5d84f06a3e1c8b27d5f0e93" }
```

```json theme={null}
"balances": [
  {
    "currency": "USD",
    "deposited": "1000",
    "withdrawn": "0.5",
    "fees": "0.3",
    "bought": "500",
    "sold": "0",
    "netBalance": "499.2",
    "committed": "100.1",
    "available": "399.1"
  }
]
```

| Field | Meaning |
| - | - |
| `deposited`, `withdrawn`, `fees` | The movements of your cash, as `get_cash_movements` lists them |
| `bought` | What your buys cost, as far as they executed |
| `sold` | What your sells brought in, as far as they executed |
| `netBalance` | `deposited − withdrawn − fees − bought + sold`: **your balance** |
| `committed` | Held and not spent yet: the unfilled part of your working buys at their limit, the fees of your trades not charged yet, and buys being placed |
| `available` | `netBalance − committed`: **what a new buy can spend**. Negative when overdrawn |

There is one entry per currency you have moved, and an empty list before your first movement.

### What a buy holds

A buy is a `LIMIT` order by `quantity`. When you place it, `quantity × limitPrice` plus its fees moves into `committed`, before the order reaches the broker; a buy your `available` does not cover answers `INVALID_ORDER` with your figures, and nothing reaches the broker. As it fills, what it executed moves from `committed` to `bought`, at the price it executed. When it ends, filled, cancelled or expired, whatever it did not spend is released. A sell adds to `sold` as it executes.

A `MARKET` buy and an order by `notional` answer `INVALID_ORDER`: neither names the price its cost would be held at.

### Movements

`get_cash_movements` lists the movements behind `deposited`, `withdrawn` and `fees`, newest first: deposits, withdrawals and fees, each with its `id`, `amount`, `currency`, `status` and `bookedAt`. Pass the `id` of the last one you hold as `before` for the next page, with `limit` up to 200.

A movement is also pushed as `cash_movement` when it is recorded for you or cancelled. Delivery is at least once: every repeat of one change carries the same `eventId`, so drop what you have seen. `CANCELLED` is final for an `id`, and a movement that is cancelled no longer counts. The push carries no balance: read `get_cash_balance_v2` for the totals, and `get_cash_movements` to catch up after a gap.

## Fund your cash with crypto

You can fund your own cash by sending USDC on an EVM chain or on Solana to a Securitize wallet, then telling us the transaction. The chains offered are the ones `get_crypto_funding` lists in `depositTo`.

Before the first deposit, ask Securitize to enable crypto funding for you and to register the wallets you send from. Only a deposit from a registered wallet is credited, and there is no message to register one: to add or remove a wallet, contact Securitize.

### 1. Read where to send it

`get_crypto_funding` answers `depositTo`, Securitize's wallets, one per chain and token with the token's contract, and `fromWallets`, the wallets Securitize registered for you. When it answers `enabled: false`, crypto funding is not enabled for you: contact Securitize. Read it again before each deposit rather than keeping the addresses: Securitize's wallets can change.

```json theme={null}
{ "type": "get_crypto_funding", "requestId": "3b9e1c7a5d2f4e86a0c4b8d1f6e2a957" }
```

```json theme={null}
{
  "enabled": true,
  "depositTo": [
    {
      "chainId": 1952,
      "token": "USDC",
      "tokenAddress": "0x1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d",
      "address": "0x8f3c6a1e9b2d4c7f0a5e3b8d1c6f9a2e4b7d0c35",
      "decimals": 6,
      "minConfirmations": 12
    }
  ],
  "fromWallets": [{ "namespace": "eip155", "address": "0x1111aaaa2222bbbb3333cccc4444dddd5555eeee" }]
}
```

### 2. Send the USDC

Send it from one of your `fromWallets` to the `address` of the chain you use. Only that exact `tokenAddress` counts (the token contract on an EVM chain, the mint on Solana): another token, or a transfer from a wallet that is not yours, is never credited. On Solana, send it from the wallet itself, not from a token account you hold for another wallet: the sender and the recipient are the wallets that own the token accounts.

### 3. Send the transaction hash

Send it with `submit_crypto_funding`, signed like `place_order`. A read-only key answers `NOT_PERMITTED`.

```json theme={null}
{
  "type": "submit_crypto_funding",
  "requestId": "8d4f2a6c1e9b4073b5a2c7e0d3f8b164",
  "timestamp": 1793631600,
  "payload": { "chainId": 1952, "txHash": "0xabab5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f6071829" },
  "signature": "3Kf9…"
}
```

`txHash` is `0x` and 64 hex digits on an EVM chain, and the base58 signature on Solana, sent as it is: Solana signatures are case-sensitive.

Once the transaction succeeded and is final, the `ack` carries `status: "CREDITED"`, the `amount` credited in USD, one for one with the USDC that arrived, and `movementId`, the movement's `id` in `get_cash_movements`. `get_cash_balance_v2` counts it at once. The credit is not pushed as `cash_movement`: the `ack` is the confirmation.

A transaction is credited once, whoever sends it: sending the same `txHash` again answers the same credit, so it is always safe to send it again.

| `code` | Meaning | What to do |
| - | - | - |
| `DEPOSIT_PENDING` | The transaction is not on chain yet, or not final | Send the same `txHash` again later |
| `DEPOSIT_REFUSED` | It will not be credited as sent. `message` says why: crypto funding is not enabled on that chain, there is no USDC transfer from one of your wallets to Securitize's, the transaction failed, or it was already credited to another account | Nothing to retry. Contact Securitize with the `traceId` if you think it should be credited |
| `UPSTREAM_UNAVAILABLE` | The chain could not be read, or no answer came in time | Send the same `txHash` again: it is never credited twice |

`submit_crypto_funding` is served on the socket only. `get_crypto_funding` is also served over HTTP, as `GET /v1/market-maker/crypto-funding`: see [Reads over HTTP](https://developers.securitize.io/cet-underlying-api/reference/http-reads.md).

## Buying power

A buy is checked twice. First against your own `available`, before it reaches the broker. Then the broker checks the account it trades through, and a buy it cannot pay for answers `INVALID_ORDER` with the message `Insufficient buying power`. Either way, [fund your cash](#fund-your-cash-with-crypto) or size the order down, and send it again. In sandbox, you can also fund it as [Sandbox funding](https://developers.securitize.io/cet-underlying-api/sandbox-funding.md) shows.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.