Scan a transaction or typed data

Simulate an unsigned EVM or Solana transaction, or check EIP-712 typed data (eth_signTypedData_v4), from the vault address and return a risk verdict. The result is advisory and is not stored. Returns 402 when your subscription does not include transaction scanning, and 503 when scanning is not enabled.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
enum
required

Payload media type. For a transaction, use the contextType a build endpoint returned with serialized. For EIP-712 typed data, use application/x-eip712+json. Scanning supports application/evm-rlp-v1+hex, application/solana-solwiretx-v1+base58 and application/x-eip712+json; other values return 400.

string
required
length between 2 and 300000

Payload to scan. For a transaction, the serialized value from a build endpoint, unchanged. EVM: 0x-prefixed RLP hex; the chain comes from its chain ID. SVM: base58 Solana wire transaction, scanned as mainnet. For EIP-712 typed data, the eth_signTypedData_v4 JSON document as a string, with exactly the top-level keys types, primaryType, domain and message. domain.chainId selects the chain. If EIP712Domain declares no chainId, a bytes32 salt holding a Polygon PoS chain ID is accepted instead, as Polygon meta-transactions use; any other salt returns 400. The document is parsed strictly, and these return 400: duplicate or case-variant keys at any depth; non-integer numbers; struct, field or type names outside [A-Za-z_][A-Za-z0-9_]*; a declared struct other than EIP712Domain that primaryType does not reach; an EIP712Domain that is not an ordered subset of string name, string version, uint256 chainId, address verifyingContract and bytes32 salt; and domain keys that differ from the declared EIP712Domain fields. A document too expensive to hash also returns 400: a struct name, field name or field type over 128 characters, a field type with over 24 array dimensions, over 64 struct types, over 64 fields in a struct, over 1,024 struct values, over 1,048,576 characters of combined encodeType text, or over 8,192 values. Values count struct fields, array elements across every dimension, and every dropped message key with its contents. Message keys a struct does not declare are dropped and not hashed, but they still follow the parsing rules; when any are dropped, the last entry in reasons says how many. The scan runs on a canonical re-serialisation of the document.

uuid
required

Vault that will sign the payload. The scan runs from the vault address on the payload chain, and the verdict is relative to that address. io.vault works out the address from the vault because an unsigned EVM transaction carries no sender and typed data names no signer.

string
^m(\/\d+)+$

HD derivation path of the signing address. Omit to scan from the vault base address for the chain. Must match the path you sign with.

Headers
string
length between 1 and 255

Key that makes this call safe to retry. Repeating the key with the same body returns the original response without running the operation again. Reusing the key with a different body is refused. Keys are scoped to you and this operation, so the same key on another operation does not collide. Keys expire some time after the original call completes. An empty or whitespace-only value is rejected. Maximum length: 255 characters.

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json