Batch processing

  1. 1.Prepare a list of prompts and parameters for batch generation
  2. 2.Use the batch API endpoint: POST /v1/batch/generate
  3. 3.Submit an array of generation requests in a single API call
  4. 4.Receive a batch ID for tracking the entire batch
  5. 5.Poll the batch status endpoint or use webhooks for completion
  6. 6.Retrieve all generated audio files when the batch completes
  7. 7.Handle partial failures gracefully with retry logic

Generate multiple audio files efficiently with batch requests. Batch processing allows you to submit multiple generation requests at once, reducing API overhead and simplifying management of large-scale audio production.

Notes

  • Pro: 50 requests/batch, Teams: 200 requests/batch, Enterprise: 1000+ requests/batch. Batches are processed in parallel with intelligent queuing.
  • Use webhooks for batch completion notifications instead of polling. Webhook payload includes success/failure status for each item in the batch.
  • Batch processing reduces API overhead and can process requests up to 5x faster than individual requests. Ideal for generating audio libraries or processing large datasets.

How would you rate the help you received from this article?

People also viewed

Streaming responses

Stream audio generation in real-time for faster results

Rate limits and quotas

Understand API rate limits and how to handle throttling

Webhooks setup

Configure webhooks for real-time notifications and events

API usage monitoring

Track your API usage and monitor credit consumption

Still need help?

Can't find what you're looking for? Our team is here to help you get the most out of Wubble.

?