Duply
← Image automation guides

Batch API

Bulk Image Generation API

Generate many branded images from records while preserving row identity, validation, retries, and output tracking.

Quick answer

Bulk image generation works best as a controlled job: validate records first, render an approved template for each valid record, and store every result against its source ID.

Best-fit use cases

Product catalogs
Certificates
Event speakers
Programmatic content

Implementation

A reliable four-step workflow

1

Prepare records

Assign a stable ID and validate required text and image fields before the batch starts.

2

Control concurrency

Use bounded parallel requests and respect plan or API limits.

3

Track every result

Record success, output URL, template version, and actionable failure for each item.

4

Retry safely

Retry temporary failures without duplicating already completed outputs.

Concrete example
trigger
A 500-item catalog export is approved
inputs
SKU, name, price, photo, badge
output
One promotion image per valid SKU
destination
DAM and ecommerce campaign feed

Frequently asked questions

Is CSV or API better for bulk generation?

Use CSV for operator-run batches and the API for scheduled, event-driven, or application-managed jobs.

Should one failed record stop the batch?

Usually no. Record the failure, continue valid items, and provide a clear retry path after correction.

Continue the workflow

Create images from CSV →Batch image generation →Production checklist →

Build one production-shaped example

Start with one approved template, realistic data, and the exact trigger your team intends to use.

Start free