Skip to main content
POST
Submit Solana transaction by id

Authorizations

Authorization
string
header
required

User bearer credential: either a Cognito JWT or an ak_ user API key. Backend integrators using HMAC must include the user API key alongside the three HMAC headers on user-scoped endpoints.

Path Parameters

txId
string
required

Server transaction id returned by the prepare endpoint. Supplied in the path for the submit alias.

Minimum string length: 1

Body

Request body for the path-based submit alias. The txId comes from the URL path; the body contains only the user's detached signature.

Request body for the path-based submit alias. The txId comes from the URL path; the body contains only the user's detached signature.

userSignature
string
required

Base64-encoded 64-byte ed25519 signature over the decoded messageBytes returned by prepare. Never send a fully signed transaction here - only the detached user signature.

Minimum string length: 1

Response

Submit response. The transaction has been broadcast to the Solana cluster. If submit is retried after a successful broadcast, the existing signature is returned.

Submit response. The transaction has been broadcast to the Solana cluster. If submit is retried after a successful broadcast, the existing signature is returned.

txId
string
required

Server transaction id.

signature
string
required

Solana transaction signature (base58).

signatureRole
string
required

Role of the signature returned (e.g., fee_payer).

Example:

"fee_payer"

status
string
required

Transaction status (e.g., submitted).

Example:

"submitted"

explorerUrl
string
required

URL to view the transaction on a Solana explorer.