getBundleStatuses

POSTTransactionsOperator+

Returns the status of up to 5 bundles submitted with `sendBundle`.

Try itSends a real request from your browser to the selected region.
POST
/

getBundleStatuses reports what happened to bundles submitted with sendBundle. Pass up to 5 bundle ids; each one comes back with its status.

Requests are relayed to the Jito Block Engine in the same region as the endpoint.

PlansOperator and above
FreeNot included
OperatorIncluded
Blade RunnerIncluded
NexusIncluded

Parameters

params is a JSON array, with values in this order: bundleIds.

1bundleIdsstring[]required

1 to 5 bundle ids returned by sendBundle.

Result

resultobject[]

One status per input bundle id, in order.

Notes

  • The example bundle ids are fake.
  • Maximum 5 bundle ids per call.
  • Counts against the plan's bundle limit, not the transaction limit.
  • Bundle requests share a per-region relay rate set by Jito. When it is full the call returns HTTP 429 with code -32005; retry after a short wait. See Errors.
  • Statuses can also be checked with getSignatureStatuses on the transaction signatures; that call does not use the bundle relay. Not accepted in batch requests, and not served on the staked or Neon Zero hostnames. Not included in the Free plan.