Skip to main content
POST
Predict in batch

How batches behave

  • Mix input types freely. Each item sets its own type, country, forceToGenderize and options.
  • Order is preserved. data[i] always matches items[i]. Use index, or your own id, to join results back.
  • Validation is all or nothing. One invalid item rejects the whole request with 400 invalid_input, and nothing is charged.
  • Execution is per item. Once the batch runs, each item succeeds or fails on its own. A 200 can contain item errors.
  • Batch items default to dataset only. Set options.ai_mode to fallback on an item if you want AI to fill gaps, as single lookups do.
  • Credits are reserved up front. A batch of 50 needs 50 available credits, and counts as one request toward your rate limit.

Handling a mixed result

Never resend a whole batch because a few items failed. Successful items were already charged. Collect the failed items and decide whether to send them again in a new, smaller batch.

Guide: enrich a contact list

Chunking, rate limiting and resuming a large import safely.

Authorizations

Authorization
string
header
required

Your Finowl API key, for example finowl_3f9a.... Create keys in the dashboard under API Keys.

Body

application/json
items
object[]
required
Required array length: 1 - 50 elements

Response

The batch ran. Each entry has either data or error.

data
object[]
required

One entry per input item, in the same order.

billing_status
string
required

Whether processing cost for this batch was confirmed. unconfirmed means do not assume the failed items were free.

Example:

"confirmed"