> ## 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=&partnerUrl= (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). # Investor Activity API > The activity of your investor account in tokenized funds, from cash and token movements to subscriptions, redemptions, reinvested distributions and holdings: pushed to your webhook and readable on request. The Investor Activity API gives you the activity of your investor account in tokenized funds, so you can keep your own books in step with Securitize's. Every movement of cash and tokens on your account is recorded by Securitize, pushed to your webhook endpoint as it happens, and readable afterwards: your cash movements, the tokens issued to you, the transfers you make, the payouts you receive and what you hold, each with the ids that tie one step to the next. ## What it covers | Activity | What you see | Guide | | - | - | - | | **Subscriptions** | Your cash arriving, applied to an issuance, and the tokens minted to you | [Reconcile a subscription](https://developers.securitize.io/investor-activity-api/reconcile-a-subscription.md) | | **Redemptions** | Your transfer back, the redemption accepted and confirmed, and the cash paid out | [Reconcile a redemption](https://developers.securitize.io/investor-activity-api/reconcile-a-redemption.md) | | **Reinvested distributions** | The cash value of a distribution and the tokens it bought | [Reconcile a subscription](https://developers.securitize.io/investor-activity-api/reconcile-a-subscription.md#reinvested-distributions) | | **Holdings** | What you hold of each token, across every wallet of your account | [Amounts](https://developers.securitize.io/investor-activity-api/amounts.md#holdings) | New kinds of activity are added as new event types and fields, announced in the [changelog](https://developers.securitize.io/investor-activity-api/changelog.md). ## What you work with | Object | What it is | Id | | - | - | - | | **Token** | One fund's token on one chain. Activity is listed per token | `tokenId` | | **Cash movement** | One movement of cash on your account: a deposit, its liquidation into tokens, a withdrawal or a refund. Read through `/deposits` | `id` of the deposit | | **Token issuance** | One minting of tokens to you, for a subscription or a reinvested distribution | `tokenIssuanceId` | | **Transaction** | One token movement on chain: an issuance to you, or a transfer you make | `id` of the transaction, `txHash` | | **Redemption** | One redemption, from accepted to paid | `id` of the redemption | | **Event** | One webhook. The deduplication key | `eventId` | The ids that join the steps are in [Identifiers](https://developers.securitize.io/investor-activity-api/identifiers.md). ## Push and pull | Channel | What it gives you | When to use it | | - | - | - | | **Webhooks** | One signed `POST` per step of your activity, as it happens | Your primary feed | | **Deposits and transactions** | Your cash movements and token transactions per token, with the keys that join them | To reconcile, and to rebuild state | | **Holdings** | What you hold of each token | To check positions against your books | | **Webhook events** | Every webhook sent to you, newest first, with its body as delivered | After an outage, to audit, to find a webhook you expected | ## The whole picture 1. **Get a bearer token** with your client credentials. [Sandbox and authentication](https://developers.securitize.io/investor-activity-api/sandbox-and-auth.md). 2. **Receive webhooks** at the endpoint your Securitize contact registered for you: verify the signature, acknowledge with a `2xx`, deduplicate on `eventId`. [Receive webhooks](https://developers.securitize.io/investor-activity-api/receive-webhooks.md). 3. **Reconcile each activity**: a subscription by `tokenIssuanceId`, a redemption by the redemption's id and the transfer's `txHash`. 4. **Check positions** with `GET /assets`, and fill any gap from the deposits, transactions and webhook events. > [card] [Sandbox and authentication](https://developers.securitize.io/investor-activity-api/sandbox-and-auth.md) > > The base URL and the token endpoint. > [card] [Receive webhooks](https://developers.securitize.io/investor-activity-api/receive-webhooks.md) > > Verify, acknowledge, deduplicate, apply. > [card] [Reconcile a subscription](https://developers.securitize.io/investor-activity-api/reconcile-a-subscription.md) > > Cash in, tokens out, joined by `tokenIssuanceId`. > [card] [Reconcile a redemption](https://developers.securitize.io/investor-activity-api/reconcile-a-redemption.md) > > Tokens in, cash out, from transfer to payout. ## Before you start * **An agreement with Securitize.** Your Securitize contact issues your client id and secret, registers your webhook endpoint and hands you its signing secret. The credentials belong to your investor account, and every answer is scoped to it. * **A public HTTPS endpoint** that answers `2xx` quickly and can verify a signature. * **An idempotent handler.** Delivery is at least once and can be out of order. Your consumer must be correct when the same event arrives twice, or a later step arrives first. ## What makes this API different * **Amounts are integers.** Every amount is a string of digits in base units, next to the `decimals` that interpret it: `"500000000"` with `decimals` `2` is 5,000,000.00. No rounding, no floating point. See [Amounts](https://developers.securitize.io/investor-activity-api/amounts.md). * **Cash and tokens are separate amounts.** A cash movement is in the currency's minor units, a token movement in the token's base units. The two meet through the fund's price, not through the API. * **Steps can arrive out of order.** The issuance transaction can arrive before the minting event. Key on ids, never on arrival order. * **Unknown values are normal.** New event types, `processType` and `paymentMethod` values are added as the API grows. Treat a value you do not know as informational and keep going. ## Not available No instructions: you subscribe and redeem through your usual channel with Securitize, and this API reports what happens. No failure events: a step that does not complete sends nothing, so check the endpoints when an expected webhook does not arrive. No self-service endpoint management: your Securitize contact registers the endpoint and rotates its secret. Every operation, field, event and error is in the API reference in the sidebar, where you can also try each call against sandbox with a token from [Get an access token](https://developers.securitize.io/investor-activity-api/api-reference/authentication/get-an-access-token.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.