Sign Transaction or Typed Data

post

/walletservice/v1/wallets/{walletId}/sign

Sign EVM transaction payloads (and EIP-712 payloads via kind=eip712) with the specified wallet.

Request

Path Parameters
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Unified sign request. Preferred shape is { blockchainKind, kind, data }. Backward-compatible legacy transaction and JSON-RPC shapes are also accepted.
Show Source
Nested Schema : chainId
Match One Schema
Show Source
Example:
1337
Nested Schema : data
Type: object
Additional Properties Allowed: true
Payload object. For transaction kinds this is tx data. For eip712 this may contain typed_data.
Nested Schema : id
Match One Schema
Show Source
Example:
1
Nested Schema : params
Type: array
Show Source
Example:
[
    {
        "from":"0xa537b178b12E40EC07c361Fa1D5bb1f6770f7262",
        "to":"0x2a58b1eb2f8821c3001eece71921ce977f6529ad",
        "data":"0x",
        "gas":21000,
        "gasPrice":0,
        "nonce":0,
        "value":0,
        "chainId":1337
    }
]
Nested Schema : items
Type: object
Examples

Security
Back to Top

Response

Supported Media Types

200 Response

Payload signed successfully.
Body ()
Root Schema : SignTransactionResponse
Type: object
Show Source
Nested Schema : signature
Type: object
Show Source
Examples

400 Response

Bad request.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : details
Type: array
Show Source

500 Response

Internal server error.
Body ()
Root Schema : Error
Type: object
Show Source
Nested Schema : details
Type: array
Show Source
Back to Top