Errors - Securitize Developers

How an error looks

{ "statusCode": 400, "message": "EXPIRED_PRICE", "error": "Bad Request" }

The error code is in message. A malformed request answers with message as a list of every field to fix:

{ "statusCode": 400, "message": ["amount must match /^\\d+$/ regular expression"], "error": "Bad Request" }

A field an operation does not define is refused the same way. A bare {"message": "..."}, with no statusCode, comes from the gateway: check the API key (Sandbox and authentication).

The investor cannot trade

403 on a price or an order means the investor is not eligible now. Securitize checks on every call.

`message`	Meaning	What to do
`UNAUTHORIZED_INVESTOR`	The investor is not verified, or their suitability (or, in the EEA, their DLT test) is not verified	Check the investor in the SecId API: status, then suitability and the DLT test. Send them back to the missing step
`WALLET_VALIDATION_FAILED`	The investor’s wallet did not pass Securitize’s screening	Link another wallet
`VALIDATION_FAILED`	The investor may not trade this stock, for example as an affiliate of its issuer	Do not offer the stock to this investor
`UNAVAILABLE_MARKET`	Securitize could not complete the check	Retry

Fetch a new price

Status	`message`	Meaning
`400`	`EXPIRED_PRICE`	The signed price is missing or expired, or the market moved since the quote. Fetch a new real-time price, show it, and prepare again
`400`	`UNAVAILABLE_MARKET`	The market is unavailable for this stock now. See Market status

Fix the order

Status	`message`	Meaning
`400`	`INVALID_AMOUNT`	An amount is not positive, has more decimals than the token allows, or the order’s value is outside the per-order limits
`400`	`INVALID_SLIPPAGE_AMOUNT`	The order cannot fill within `minOutputAmount`
`400`	`MAX_POSITION`	A buy would take the investor’s position in the stock over its limit
`404`	`SYMBOL_NOT_FOUND`	The symbol or contract address is not one Securitize trades, the buy and sell addresses are swapped, or `signedPrice` is for another stock

Submitting

Status	`message`	Meaning	What to do
`400`	`UNAVAILABLE_MARKET`	A signature is missing or invalid, the transaction was modified, its 120 seconds passed, it was already submitted, `tokenId` does not match, or the market is unavailable	Prepare the order again
`409`	`TRADE_IN_PROGRESS`	The same signed transaction is already being submitted	Do not resubmit. Follow the first submission on chain

Linking a wallet

`message`	What to do
`INVESTOR_WALLET_ALREADY_ADDED`	Already linked to this investor: nothing to do
`WALLET_ALREADY_IN_USE`	Linked to another investor. Use another wallet
`MAX_WALLETS_REACHED`	The investor holds the most wallets allowed. Contact Securitize

Limits and faults

Status	Meaning	What to do
`429`	Over the limit: one request a second and sixty an hour per investor for real-time prices and for each trading call	Back off
`500`, `502`	A fault on Securitize’s side	Retry a price or a prepare. Never resubmit a signed transaction: read the chain

Treat a code you do not recognise as a refusal of that call.

What is safe to retry

Call	Repeat it
Prices and statistics	Safe
Wallet status, agreement message	Safe
Prepare an order	Safe. Each prepare builds a new transaction; one that is never signed expires unused after 120 seconds
Submit a signed transaction	Not safe. Each prepared transaction executes once. If you do not know whether a submission went through, look up its hash on chain before doing anything else

Getting help

When you contact Securitize about a response, send the operation and the time of the call, the investorId, the status and message you received, and for a submitted order its transaction hash. Never send your API key.