curl --request POST \
--url https://partners-api.sandbox.securitize.io/investors/v1/onboarding-reliance/investors/{investorId}/wallets \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"address": "0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed",
"blockchainType": "evm"
}
'{
"address": "0x5aaeb6053f3e94c9b9a09f33669435e7ef1beaed",
"blockchainType": "evm"
}Register a wallet
Associates a blockchain address with the investor and adds it to your list of that investor’s wallets. You vouch that the investor controls the address: there is no signature or challenge. Any investor status works, individual or entity, and so does an investor you have limited access to.
Two families, not chains: evm (Ethereum and every EVM chain; you never name the chain) and solana. An EVM address is stored and returned in lower case; a Solana address exactly as sent.
An address belongs to one investor across all of Securitize. An address another investor holds answers 409 wallet_conflict. An address this investor already holds — registered by you, by another partner or by the investor — answers 201 and joins your list, so repeating the call is safe.
Each investor can hold a limited number of wallets per family; Securitize can raise the limit. Registering does not let the wallet receive tokens: whitelist it on a token with POST /investors/{investorId}/wallets/whitelist. There is no call to remove a wallet.
curl --request POST \
--url https://partners-api.sandbox.securitize.io/investors/v1/onboarding-reliance/investors/{investorId}/wallets \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"address": "0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed",
"blockchainType": "evm"
}
'{
"address": "0x5aaeb6053f3e94c9b9a09f33669435e7ef1beaed",
"blockchainType": "evm"
}Authorizations
OAuth 2.0 client credentials. Exchange the client id and secret Securitize issued you for a bearer token at the token URL (the host root, not under the base URL), with grant_type=client_credentials; the token lasts 2 hours and goes in the Authorization: Bearer header of every request. No scope is needed. The token identifies your partner account, so you never send a partner id, and every record you create is scoped to you.
Path Parameters
Body
A wallet to register for the investor.
Response
Registered, or already held by this investor. The wallet is in your list.