Overview
The Get Current Batch endpoint retrieves the currently active flywheel batch for a specified token. This is useful for checking if there’s already an ongoing batch operation before creating a new one, or for getting the status of the current batch without needing to know the specific batch ID. Returnsnull if no current batch exists for the token.
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.Request
This endpoint requires no request body. The current batch is determined based on the authenticated API key.Example Request
Response Body
On success, the API returns either:- A JSON object containing the current batch information (same structure as /batch/{batchId})
- nullif no current batch exists for the token
Example Response (Current Batch Exists)
Example Response (No Current Batch)
Batch Status Values
When a current batch exists, it will have one of these 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 (may still be “current” briefly). | 
| FAILED | Batch execution failed. | 
Use Cases
- Pre-Creation Check: Verify no active batch exists before creating a new one.
- Status Monitoring: Get the current batch status without needing to store batch IDs.
- Workflow Management: Determine if your application should wait for current operations to complete.
- Error Recovery: Check if a batch is stuck in a particular state and needs intervention.
- Dashboard Display: Show users the current state of their token’s flywheel operations.
Integration Patterns
Before Creating New Batch
Status Monitoring Loop
Error Codes
The current batch endpoint can return specific error codes.| Error Code | Status | Description | 
|---|---|---|
| ERR_BATCH_CURRENT_FAILED | 500 | Failed to retrieve current batch information. | 
Example Error Response
Important Notes
- 
Null Response: A nullresponse is normal and indicates no current batch exists for the token.
- Current Definition: A batch is considered “current” if it’s the most recent batch that hasn’t reached a final state.
- 
State Transitions: Once a batch reaches EXECUTEDorFAILEDstatus, it may no longer be considered “current” depending on your implementation.
- Race Conditions: In high-frequency applications, check for current batch immediately before creating new ones to avoid conflicts.
- Token Scoping: This endpoint only returns batches for the specific token ID provided, ensuring proper isolation between different tokens.
Authorizations
Response
Current batch information or null if no current batch exists.
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).