Overview
The Get Batch Status endpoint allows you to retrieve detailed information about a flywheel batch, including its current status, execution results, and pipeline details. This is useful for monitoring the progress of batch operations and checking execution results.Authentication
This endpoint requires API key authentication. The API key must have eitherburn or airdrop scopes.
To authenticate, provide your API key in the x-believe-api-key request header.
Example:
Rate Limiting
Requests to this endpoint are rate-limited to 10 requests per second per API key.Path Parameters
| Parameter | Type | Required | Description | 
|---|---|---|---|
| batchId | string | Yes | The UUID of the batch to retrieve status for. | 
Example Request
Response Body
On success, the API returns a JSON object containing the complete batch information:| Field | Type | Description | 
|---|---|---|
| id | string | The unique batch identifier (UUID). | 
| flywheelId | string | The flywheel this batch belongs to. | 
| tokenId | string | The token ID associated with this batch. | 
| mintAddress | string | The Solana mint address for the token. | 
| status | string | Current batch status (see status values below). | 
| batchIndex | string | The multisig batch index used for execution. | 
| vaultIndex | string | The vault index within the multisig. | 
| multisig | string | The multisig wallet address. | 
| vaultAddress | string | The vault address for token operations. | 
| initResult | Object | (Optional) Results from the batch initialization process. | 
| executeResult | Object | (Optional) Results from the batch execution process. | 
| dateCreated | string | ISO 8601 timestamp when the batch was created. | 
| dateUpdated | string | ISO 8601 timestamp when the batch was last updated. | 
Batch Status Values
| Status | Description | 
|---|---|
| AVAILABLE_TO_QUEUE | Batch has been created but not yet finalized for execution. | 
| FINALIZED | Batch has been finalized and is ready for execution approval. | 
| EXECUTED | Batch has been successfully executed. | 
| FAILED | Batch execution failed. | 
Init Result Object (Optional)
Present when status isFINALIZED or later.
| Field | Type | Description | 
|---|---|---|
| total | number | Total number of setup transactions processed. | 
| totalSuccessful | number | Number of setup transactions that succeeded. | 
| totalFailed | number | Number of setup transactions that failed. | 
| successfulExecutions | Array | Array of successful bundle executions during setup. | 
| failedTxMsg | string | (Optional) Error message if setup failed. | 
| batchIndex | number | The batch index used in the multisig. | 
Execute Result Object (Optional)
Present when status isEXECUTED or FAILED.
| Field | Type | Description | 
|---|---|---|
| total | number | Total number of pipeline transactions. | 
| totalSuccessful | number | Number of pipeline transactions that executed successfully. | 
| totalFailed | number | Number of pipeline transactions that failed. | 
| successfulExecutions | Array | Array of successful bundle executions. | 
| failedOnTransactionIndex | number | (Optional) Transaction index where failure occurred. | 
| failedStartTransactionIndex | number | (Optional) Starting index of the failed transaction batch. | 
| failedTxMsg | string | (Optional) Error message describing the failure. | 
Example Response (Finalized Batch)
Example Response (Executed Batch)
Use Cases
- 
Monitor Batch Progress: Check if a batch has moved from FINALIZEDtoEXECUTEDstatus.
- Retrieve Execution Results: Get detailed transaction hashes and bundle IDs after execution.
- 
Debug Failed Batches: Examine error messages and failure details when status is FAILED.
- Audit Trail: Review the complete lifecycle of a batch operation with timestamps.
- Integration Status Checks: Poll this endpoint to determine when to proceed with next steps in your application flow.
Error Codes
The batch status endpoint can return specific error codes.| Error Code | Status | Description | 
|---|---|---|
| ERR_BATCH_NOT_FOUND | 404 | No batch exists with the provided batch ID. | 
Example Error Response
Integration Tips
- Polling Strategy: Use this endpoint to poll for status changes after calling batch init or execute.
- Error Handling: Check both the HTTP status and the batch status field for complete error information.
- Transaction Verification: Use the returned transaction hashes to verify operations on Solana explorers.
- Status Transitions: Batches typically progress: AVAILABLE_TO_QUEUE→FINALIZED→EXECUTED/FAILED.
Authorizations
Path Parameters
The UUID of the batch to retrieve status for.
Response
Successful batch status retrieval.
The unique batch identifier (UUID).
The flywheel this batch belongs to.
The token ID associated with this batch.
The Solana mint address for the token.
Current batch status.
Available options: 
AVAILABLE_TO_QUEUE, FINALIZED, EXECUTED, FAILED The multisig batch index used for execution.
The vault index within the multisig.
The multisig wallet address.
The vault address for token operations.
ISO 8601 timestamp when the batch was created.
ISO 8601 timestamp when the batch was last updated.
Results from the batch initialization process (optional).
Results from the batch execution process (optional).