APIAHATalk to us
← All features

Feature · Throughput

Batch reads for multi-target workflows.

Profiles, posts, pins, channels, or properties in one call — still capped, still metered, still cache-aware.

What this unlocks

Capability outcomes, not availability claims.

Batch routes exist so agencies and diligence desks avoid N+1 chatter. They are not a license to ignore per-product rate and record limits.

01

Documented ceilings

Each batch path declares how many targets or records it accepts.

02

Per-item honesty

Failed targets surface as structured misses where the contract supports partial success.

03

Metered fairly

Usage formulas bill the work performed, not a flat vanity request count alone.

Evidence-gated surface

Launch routes that back this feature.

Paths below are taken from each product's committed route manifest. Catalog status still decides whether buyers may call them.

Endpoint presence is not a public-availability claim. Review the canonical catalog before integrating.