Skip to main content
POST
Sign Authorization (EIP-7702)

Authorizations

X-API-Key
string
header
default:sk_your_secret_key_here
required

Your partner secret key (server-side only)

Headers

X-Request-Id
string<uuid>

UUID for request tracing. Para returns one if omitted.

Idempotency-Key
string

Unique key for safe retries on POST endpoints. If a request with the same key is received within 24 hours, the original response is returned without re-executing. Recommended format: UUID v4. Max length 256 characters. Returns 422 if the same key is reused with a different request body. Returns 409 if a request with the same key is still being processed.

Maximum string length: 256

Path Parameters

walletId
string<uuid>
required

Wallet UUID. A malformed or inaccessible wallet ID returns 404.

Example:

"0a1b2c3d-4e5f-6789-abcd-ef0123456789"

Body

application/json
authorization
object
required

Provide address or contractAddress as the delegation target. If both are supplied, contractAddress is used.

Response

Signed authorization

address
string
required

Contract address the authorization delegates to.

Example:

"0x1234567890abcdef1234567890abcdef12345678"

chainId
integer
required

Chain ID from the authorization.

Example:

1

nonce
integer
required

Nonce from the authorization.

Example:

0

r
string
required

ECDSA signature r component (hex with 0x prefix).

Example:

"0xa1b2c3..."

s
string
required

ECDSA signature s component (hex with 0x prefix).

Example:

"0xd4e5f6..."

yParity
enum<integer>
required

EIP-7702 parity bit (0 or 1). Unlike other signing endpoints that return v (27/28), this uses yParity per the EIP-7702 spec.

Available options:
0,
1
Example:

0

signature
string
required

Raw hex-encoded 65-byte signature without 0x prefix (r + s + v).

Example:

"a1b2c3d4e5f6..."