Skip to main content
POST
Submit a signed transaction

Authorizations

Authorization
string
header
required

Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header.

Path Parameters

transactionId
string
required

Transaction id (from an action's transactions[].id).

Body

application/json

A signed payload (with its actionId) or a broadcast tx hash — at least one is required.

signedPayload
string
required

The signed payload for the venue to broadcast.

Example:

"0x1234567890abcdef..."

actionId
string
required

Required when submitting a signedPayload (omit it for a transactionHash self-broadcast). The id of the action this transaction belongs to. For an EIP-712 transaction, Portal verifies the signature recovers to the account the action was built for before forwarding, and returns a 400 if it does not (id: PERPS_SIGNATURE_ADDRESS_MISMATCH), if the signature cannot be recovered at all (id: PERPS_SIGNATURE_INVALID), or if the payload cannot be hashed for verification (id: PERPS_SIGNATURE_UNVERIFIABLE). Requiring it guards against a signed action being forwarded without the signer being verified.

Example:

"550e8400-e29b-41d4-a716-446655440001"

transactionHash
string

The hash of a transaction you broadcast yourself.

Example:

"0xabcdef1234567890..."

Response

Submission result

data
object
required

Result of submitting a signed transaction or broadcast hash.