REST signing types

Import

These types are exported by @getpara/rest-sdk.

import type { WalletType, RestSigningInitiator, RestSigningRequestContext, SignRawRequest, SignMessageRequest, SignTransactionRequest, SignTypedDataRequest, SignAuthorizationRequest, AutoRetrySignTransactionRequest, AutoRetrySignTransactionResponse } from "@getpara/rest-sdk";

Request initiator

Ordinary signing requests take an optional initiatorUserId, defined by RestSigningInitiator. Managed autoRetry requests do not accept an initiator. Set it to the Para user ID of the linked user who asked for the signature. That user cannot approve or reject the request’s approval case. An ID that is not a UUID, or a user with no wallet connected to your app, fails with 400 INVALID_REQUEST and the message user is not linked to this app.

interface RestSigningInitiator { initiatorUserId?: string; }

Review ID

Ordinary signing requests also take an optional reviewId. Managed autoRetry calls require current policy allow without a transaction-bound approval and do not accept reviewId. After your backend approves an ordinary review, you can add its reviewId when you resend the identical request with the same Idempotency-Key. Para still checks that the request and the active policy match the review. Each ordinary signing and transfer request type extends RestSigningRequestContext, which adds reviewId to RestSigningInitiator.

interface RestSigningRequestContext extends RestSigningInitiator { reviewId?: string; }

Raw messages and EVM messages

signRaw takes data and an optional encoding, while signMessage takes a message. Both return a signature.

interface SignRawRequest extends RestSigningRequestContext { data: string; encoding?: 'hex'; walletType?: WalletType; }
interface SignRawResponse { signature: string; }
interface SignMessageRequest extends RestSigningRequestContext { message: string; }
interface SignMessageResponse { signature: string; }

Transactions and typed data

When you sign EIP-712 typed data through the viem v2 or ethers v6 integration or the wagmi connector, the Para SDK sends the typed data with its hash. Para checks that the two match and evaluates the request as sign_typed_data, the same as the REST API’s sign-typed-data route, so request.typedData.primaryType, request.approvalLike and the chain ID from the typed data’s domain apply. Para evaluates these SDK requests as sign_message, with no chain ID: EIP-7702 authorizations, typed data signed through the viem v1 or ethers v5 integration, and a typed data hash that your code signs with signMessage. The sign_authorization action and its facts apply only to the REST API’s sign-authorization route, which the REST SDK calls.

interface EvmSignTransactionRequest {
  to: string; chainId: string | number; type: 0 | 2;
  value?: string; data?: string; nonce?: number; gasLimit?: string;
  maxFeePerGas?: string; maxPriorityFeePerGas?: string; gasPrice?: string;
}
interface SignTransactionRequest extends RestSigningRequestContext {
  transaction: EvmSignTransactionRequest | string;
  autoRetry?: never;
  broadcast?: boolean; network?: 'SOLANA' | 'SOLANA_DEVNET' | 'SUI' | 'SUI_TESTNET' | 'SUI_DEVNET'; networkPassphrase?: string;
}
interface EvmAutoRetrySignTransactionRequest extends EvmSignTransactionRequest {
  accessList?: Array<{ address: string; storageKeys: string[] } | [string, string[]]>;
}
interface EvmAutoRetryAuthorization { maxExecutionFeeWei: string; expiresAt: string; }
interface SolanaAutoRetryAuthorization { maxExecutionFeeLamports: string; expiresAt: string; }
type AutoRetrySignTransactionRequest =
  | { transaction: EvmAutoRetrySignTransactionRequest; broadcast: true; walletType?: 'EVM'; autoRetry: EvmAutoRetryAuthorization }
  | { transaction: string; broadcast: true; walletType?: 'SOLANA'; network?: 'SOLANA' | 'SOLANA_DEVNET'; versioned?: false; autoRetry: SolanaAutoRetryAuthorization };
type AnySignTransactionRequest = SignTransactionRequest | AutoRetrySignTransactionRequest;
interface SignTransactionResponse { signedTransaction: string; txHash?: string; transactionId?: string; autoRetry?: never; }
interface AutoRetrySignTransactionResponse extends RestTransaction {
  autoRetry: RestAutoRetryDetails; signedTransaction?: never; txHash?: never;
}
type AnySignTransactionResponse = SignTransactionResponse | AutoRetrySignTransactionResponse;

interface TypedDataPayload {
  domain: Record<string, unknown>;
  types: Record<string, Array<{ name: string; type: string }>>;
  primaryType: string;
  message: Record<string, unknown>;
}
interface SignTypedDataRequest extends RestSigningRequestContext { typedData: TypedDataPayload; }
interface SignTypedDataResponse { signature: string; }

accessList belongs to EvmAutoRetrySignTransactionRequest; ordinary signing does not preserve access lists. For signTransactionWithAutoRetry, pass options.idempotencyKey and persist the complete request before submitting. The original deadline must be in the next 24 hours and is never renewed by replay. Read status, autoRetry.state, attempts and monitoring.winningHash through getRestTransaction. See Automatic fee retry for supported shapes and the transaction lookup fields.

EIP-7702 authorization

The authorization payload identifies the contract or address, chain ID and nonce. The response includes the signature and its normalized fields.

type SignAuthorizationPayload =
  ({ contractAddress: string; address?: string } | { address: string; contractAddress?: string }) &
  { chainId: string | number; nonce: number };
interface SignAuthorizationRequest extends RestSigningRequestContext { authorization: SignAuthorizationPayload; }
interface SignAuthorizationResponse {
  address: string; chainId: number; nonce: number; r: string; s: string; yParity: 0 | 1; signature: string;
}

Overview

Client Methods

Actions

React Hooks

Signers & Integrations

Smart Accounts

Wallet Connectors

REST SDK

Types & Configuration

REST signing types

Import

Request initiator

Review ID

Raw messages and EVM messages

Transactions and typed data

EIP-7702 authorization

​Import

​Request initiator

​Review ID

​Raw messages and EVM messages

​Transactions and typed data

​EIP-7702 authorization

Import

Request initiator

Review ID

Raw messages and EVM messages

Transactions and typed data

EIP-7702 authorization