> ## 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).

# Documents

> Which documents each investor needs, the file rules, the test files, and what each refusal means.

One document per call, with all of its files, sent as JSON with each file base64-encoded or as `multipart/form-data` with each file as a part of its own (see [Two ways to send the files](#two-ways-to-send-the-files)). There are two kinds of document.

| | Identity document | Company document |
| - | - | - |
| For | An individual investor, or a person key party | A company key party, or an entity's own file |
| Types | `passport`, `driving-licence`, `national-identity-card`, `residence-permit` | 32 types, listed in the [API reference](https://developers.securitize.io/api-reference/documents/add-a-document-to-an-investor.md) |
| Files per call | `passport`: 1, `side: "front"`. The others: 2, one `front` and one `back` | Exactly 1, no `side` |
| Other fields | `documentNumber` and `expiresAt` required | None |
| File types | `image/jpeg`, `image/png` | `image/jpeg`, `image/png`, `application/pdf` |
| Sent to | `POST /investors/{investorId}/documents` (individual) or `…/key-parties/{keyPartyId}/documents` (person key party) | `…/key-parties/{keyPartyId}/documents` (company key party) or `POST /investors/{investorId}/documents` (entity) |

Which company documents a corporate shareholder needs depends on its legal form: see [Onboard a company](https://developers.securitize.io/secid-api/onboard-a-company.md#3-send-their-documents). An entity's own company documents are optional.

A signed tax form (W-9, W-8BEN, W-8BEN-E) is not a document: it goes to its own route. See [Send a tax form](https://developers.securitize.io/secid-api/tax-forms.md).

## Two ways to send the files

Both document routes take either body, with the same rules and the same answers. Choose per call; nothing else changes.

| | JSON | `multipart/form-data` |
| - | - | - |
| Each file | Base64 in `files[].content`, with its `mime` and `side` | A part of its own, sent as the file itself |
| Largest file | 10 MB | 20 MB |
| `type`, `documentNumber`, `expiresAt` | JSON fields | Text parts with the same names |
| Side of the file | `side` on each file | The name of the part: `front`, `back` |
| Company document | One entry in `files`, no `side` | One part named `file` |
| File type | `mime`, checked against the file's first bytes | Read from the file's first bytes; the part's own type and file name do not matter |

**Send files over 10 MB as multipart.** Base64 makes a file a third larger, so a 20 MB scan would be a request of almost 60 MB as JSON; as multipart it travels at its own size, and your client does not need to encode it.

### Multipart

Let your HTTP client build the body. It writes the `content-type` header itself, with the boundary that separates the parts: do not set `content-type` yourself, since a header without that boundary answers `400 invalid_document`. With curl, each `-F` adds one part:

```bash theme={null}
# Passport: one front part
curl -X POST "$BASE/investors/$INVESTOR_ID/documents" -H "Authorization: Bearer $ACCESS_TOKEN" \
  -F type=passport -F documentNumber=P-IND1-0000 -F expiresAt=2032-01-01 \
  -F front=@passport.png

# Driving licence, national identity card or residence permit: front and back in the same call
curl -X POST "$BASE/investors/$INVESTOR_ID/key-parties/$KEY_PARTY_ID/documents" -H "Authorization: Bearer $ACCESS_TOKEN" \
  -F type=driving-licence -F documentNumber=DL-0000000 -F expiresAt=2030-06-30 \
  -F front=@licence-front.jpg -F back=@licence-back.jpg

# Company document: one file part, PDF allowed
curl -X POST "$BASE/investors/$INVESTOR_ID/documents" -H "Authorization: Bearer $ACCESS_TOKEN" \
  -F type=certificate-of-registration -F file=@certificate.pdf
```

The parts a document takes:

| Document | Text parts | File parts |
| - | - | - |
| `passport` | `type`, `documentNumber`, `expiresAt` | `front` |
| `driving-licence`, `national-identity-card`, `residence-permit` | `type`, `documentNumber`, `expiresAt` | `front` and `back` |
| Any company type | `type` | `file` |

A file part that does not belong to the document (a `file` part on a passport, a `back` part on a passport, a `front` part on a company document), a part with another name, an empty file or more than two files answer `400 invalid_document`, and `details` names the part when it can. Text parts with other names are ignored, as unknown JSON fields are.

### JSON

Each file goes in `files[]` with its `mime`, its `side` (identity documents) and its `content` in base64:

* **Encoding**: plain base64. A `data:<mime>;base64,` prefix, line breaks, the URL-safe alphabet and missing padding are all accepted.
* **`mime` must match the file**: it is checked against the file's first bytes.
* **The whole request** is at most about 31 MB, enough for both sides of a document at 10 MB each.

The [API reference](https://developers.securitize.io/api-reference/documents/add-a-document-to-an-investor.md) has the JSON and multipart shapes side by side, with examples of each.

## File rules

* **Size**: each file at most 10 MB as JSON (the file's own size, before base64; about 13.3 MB once encoded), or 20 MB as multipart. Above 20 MB, reduce the scan rather than splitting it: one call takes one document. Check the size before sending: an oversized file is refused only after it has been uploaded.
* **File types**: identity documents are JPEG or PNG; company documents are JPEG, PNG or PDF.
* **Identity files are read optically**, so they must be real, legible images. A long edge of 1,000 to 1,500 pixels and JPEG quality 80 to 90 work well.
* `expiresAt` is a date, `YYYY-MM-DD`; it is returned exactly as you send it.

## Test files

Use these in sandbox; they pass every check:

| File | Use it as |
| - | - |
| [passport.png](https://developers.securitize.io/secid-api/fixtures/passport.png) | Identity document (`passport`, `image/png`) |
| [company-document.png](https://developers.securitize.io/secid-api/fixtures/company-document.png) | Company document (`image/png`) |

Send them as they are in a multipart part, or encode one for the JSON `content` field with:

```bash theme={null}
base64 -i passport.png | tr -d '\n'      # macOS
base64 -w0 passport.png                  # Linux
```

## Three ways a document is refused

Nothing is stored in any of them, so you can correct and send again.

| Status | `code` | Means | Fix |
| - | - | - | - |
| `400` | `invalid_document` | The metadata is wrong: unknown `type`, wrong number of files or `side`, missing `documentNumber` or `expiresAt`, `content` that is not base64, or a `mime` that does not match the bytes. As multipart: a file part that does not belong to the document, an empty file, or a body your client did not build (a `content-type` without its boundary) | The request, not the image |
| `415` | `mime_not_supported` | The file type is not accepted for this kind of document, for example a PDF passport; or a body that is neither JSON nor `multipart/form-data` | Convert the file, or the body |
| `422` | `document_rejected` | The image could not be read: truncated, corrupt or illegible | Send a better scan, both sides |

A document of the wrong kind for its holder (an identity document for a company, a company document for a person) answers `422 business_rule_violation`. A file over its limit (10 MB as JSON, 20 MB as multipart) answers `413 payload_too_large`, and nothing is stored either.

## Uploading again

Each call stores a new document; uploads are not deduplicated. Re-send a document only when:

* it was refused (`400`, `415`, `422`): nothing was stored;
* it answered `502 file_upload_failed`: nothing was stored;
* it answered `502 document_outcome_unknown` or `502 verification_handoff_failed`: the document was kept, and sending it again is safe; the extra copy is harmless.

Documents listed by `GET /investors/{investorId}?include=documents` or `GET /investors/{investorId}/key-parties` were all accepted: refused documents are never stored. A two-sided document appears as two entries, one per side. There is no call to delete a document.


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