Skip to main content
TXResponse frames are JSON text messages serialized as:
This page lists every TXResponse variant emitted by the socket and the fields you can expect in body.

Shared body fields

These fields are reused across multiple TXResponse variants. The socket also injects request context onto many responses when it can resolve the originating request: display.fields entries use this shape:

All TXResponses

ingress_ack

The request envelope was parsed and accepted by the socket. Example:

dispatch

The request was dispatched to a handler or proxy route.

mint

The created token mint is known.

metadata

Metadata was uploaded and the URI is available.

sell

Sell-specific progress event. The body only carries correlation fields.

submit

The backend submitted a transaction upstream.

confirmed

The transaction confirmed. This is terminal.

success

The request succeeded. This is terminal.

failure

Submission happened, but the request failed to confirm successfully. This is terminal.

error

The request failed before success. This is terminal.

simulation

Simulation-only result. This can be terminal when the request was run in simulation mode.

four_meme_token

Four.meme access token update for a wallet.

Non-TXResponse frame

rate_limit_hit is sent by the socket, but it is not part of the TXResponse enum. It uses the same outer JSON shape:
Treat confirmed, success, failure, error, and terminal simulation responses as the end of a request.