API Reference

Transaction Status

Query the current status of a previously submitted transaction.

GET/v1/status/:signature

Request

Authenticate with your API key (Bearer header or ?api-key= query). This endpoint only returns transactions submitted through your own BoltTx account — you cannot look up other users' submissions, and signatures that never went through BoltTx return 404. The response is BoltTx delivery telemetry only (submitted_at, confirmed_at, latency_ms, slot, which API key sent it). For on-chain commitment levels, confirmation depth, or transaction error details, query your own Solana RPC's getSignatureStatuses — BoltTx is a delivery service, not a chain query service. Queries draw from a separate Query bucket, so polling does not consume your tx-submission TPS budget; the cap is 2× your Send TPS (Starter: 16 q/s, Growth: 60 q/s, Pro: 160 q/s, Whale: 300 q/s).

Scoped to your account

Just like the dashboard logs, this endpoint only returns transactions submitted via API keys you own. Signatures sent by other users — or signatures that never went through BoltTx at all — return 404. This protects your trading footprint and keeps BoltTx from being abused as a free public RPC.

Headers

Headers	Value	Required
Authorization	Bearer YOUR_API_KEY	Required

Path Parameters

Parameter	Type	Description
signature	string	The transaction signature returned by the send endpoint

Example Request

cURL

curl https://bolttx.io/v1/status/5xKnR8qXeVm3pN... \
  -H "Authorization: Bearer YOUR_API_KEY"

URL auth (alternative)

If setting headers is inconvenient — e.g. testing in a browser, sharing a quick lookup link, or a tool that doesn't support custom headers — you can authenticate by appending your key as a query parameter. Both ?api-key=YOUR_KEY and ?api_key=YOUR_KEY are accepted and are functionally identical to the Authorization header.

cURL

curl "https://bolttx.io/v1/status/5xKnR8qXeVm3pN...?api-key=YOUR_API_KEY"

Heads up: URL-encoded keys show up in server logs, reverse-proxy logs, and browser history. Prefer the Authorization header for production and high-frequency polling. URL auth is best for quick debugging and prototyping.

Response

Success (200)

{
  "signature": "5xKnR8qXeVm3pN...",
  "status": "confirmed",
  "submitted_at": "2026-04-14T08:21:33Z",
  "confirmed_at": "2026-04-14T08:21:33.412Z",
  "latency_ms": 412,
  "slot": 234567890,
  "api_key_name": "prod-bot-1"
}

Response Fields

Field	Type	Description
signature	string	The transaction signature
status	string	BoltTx-tracked lifecycle: sent (submitted, awaiting on-chain confirmation), confirmed (succeeded), failed (executed but reverted)
submitted_at	string	ISO-8601 UTC timestamp when BoltTx accepted and submitted the transaction
confirmed_at	string \| null	ISO-8601 UTC timestamp of on-chain confirmation, measured by BoltTx's in-house tracker. Null until the transaction reaches a terminal state.
latency_ms	number \| null	Submit-to-confirm wall-clock latency in milliseconds, measured end-to-end by BoltTx. Null until confirmed.
slot	number \| null	Slot in which the transaction was processed
api_key_name	string	Friendly name of the API key that submitted the transaction (so you can tell which bot or service sent it)

Status Values

Status	Description
sent	Transaction has been submitted to the network; awaiting on-chain confirmation
confirmed	Transaction confirmed on-chain (executed successfully)
failed	Transaction was included in a block but execution failed. Query your own Solana RPC for the on-chain error details.

Error Codes

Code	Message	Description
400	Invalid signature	Malformed signature format
401	Unauthorized	Missing or invalid API key
404	Not found	Signature was not submitted via this account. /v1/status only returns transactions you sent through BoltTx; signatures from other users or off-platform are never exposed.
429	Query rate limit exceeded	Per-user query budget exhausted; cap is 2× your plan's send TPS, shared across all your API keys (creating more keys does not raise the limit — upgrade your plan instead)
500	Internal error	Database error while looking up the transaction

Tracking your transactions

Your transaction signature is available locally the moment you sign the transaction — no need to wait for our response. Use it to subscribe to confirmations directly via your Solana RPC node, or poll this endpoint when you need a quick status check.

Batch Send Anti-MEV