THthirdweb
Wallets

Sign Typed Data

Signs structured data according to the EIP-712 standard using the specified wallet. This is commonly used for secure message signing in DeFi protocols, NFT marketplaces, and other dApps that require structured data verification. The typed data includes domain separation and type definitions for enhanced security.

Authentication: This endpoint requires project authentication and wallet authentication. For backend usage, use x-secret-key header. For frontend usage, use x-client-id + Authorization: Bearer <jwt> headers.

post/v1/wallets/sign-typed-data

Request

  • Base URL
    https://api.thirdweb.com
  • Auth
    HTTP bearer and API key in header x-client-id

Request body

fromstring required

The wallet address or ENS name that will sign the typed data.

chainIdinteger required

The blockchain network identifier for EIP-712 domain separation.

messageobject required

The structured data to be signed, matching the defined types schema.

primaryTypestring required

The primary type name from the types object that defines the main structure being signed.

typesobject required

Type definitions for the structured data, following EIP-712 specifications.

Example request

{
  "from": "0x1234567890123456789012345678901234567890",
  "chainId": 1,
  "domain": {
    "name": "MyDomain",
    "version": "1",
    "chainId": "1",
    "verifyingContract": "0x1234567890123456789012345678901234567890"
  },
  "message": {
    "name": "foo"
  },
  "primaryType": "MyType",
  "types": {
    "MyType": [
      {
        "name": "name",
        "type": "string"
      }
    ]
  }
}

Response

Typed data signed successfully. Returns the EIP-712 compliant signature that can be used for on-chain verification.

Changes

No recorded changes to this operation across all 5 revisions of this API.