Overview
POST /api/v1/broadcast/batch co-signs and broadcasts up to 25 sponsored transactions in one request. Each transaction is processed concurrently and independently — one failure does not abort the rest.
The endpoint always returns HTTP 200. Check each item’s error field for per-item failures.
Request
Headers:| Field | Type | Required | Description |
|---|---|---|---|
transactions | array | Yes | Array of transaction objects. Max 25. |
transactions[].txHex | string | Yes | Signed sponsored transaction hex. |
transactions[].feeAmount | string | No | Fee in token micro-units. Required for USER_PAYS, omit for DEVELOPER_SPONSORS. |
userId | string | No | User identifier override. Falls back to the API key owner. |
Response
| Field | Description |
|---|---|
results | Per-item outcome. Successful items include txid and status. Failed items include error. |
summary.total | Total number of transactions submitted. |
summary.succeeded | Number successfully sponsored and broadcast. |
summary.failed | Number that failed (replay, validation error, etc.). |
Rate Limits
Batch limits are tighter than single broadcast because one call can sponsor up to 25 transactions.| Limit | Value |
|---|---|
| Per API key | 5 requests / 60s |
| Per IP | 10 requests / 60s |
429 Too Many Requests with a Retry-After header.
SDK Usage
Use Cases
- Airdrops — distribute tokens to multiple users in one call
- Queue processing — drain a backlog of pending sponsored transactions
- Multi-step flows — execute a sequence of contract calls on behalf of multiple users simultaneously