Batch endpoints for high-volume use
6 min read Updated February 1, 2026
Overview
Batch endpoints let you process multiple items in a single API call. This reduces HTTP overhead, stays within rate limits, and simplifies your code for bulk operations.
Available Batch Endpoints
| Endpoint | Max Batch Size | Typical Latency |
|---|---|---|
| `/v1/compliance/restricted-party-screening` | 1,000 parties | 2–5 seconds |
| `/v1/hs/classify` (batch) | 100 items | 3–8 seconds |
| `/v1/compliance/export-license` | 50 items | 1–3 seconds |
Batch Screening Example
Screen multiple parties in one request:
bash
curl -X POST https://api.compliancegrid.ai/v1/compliance/restricted-party-screening \
-H "Authorization: Bearer $CG_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"parties": [
{"name": "Acme Corp", "country": "US"},
{"name": "Global Trading Ltd", "country": "DE"},
{"name": "Pacific Imports", "country": "JP"}
]
}'Billing
Batch requests count as 1 API call regardless of batch size. This makes them significantly more cost-effective than individual requests for bulk operations.
Best Practices
- Fill batches as close to the max size as possible to maximize efficiency
- Implement partial failure handling — some items in a batch may fail while others succeed
- Use batch endpoints for nightly re-screening, onboarding flows, and data migration
- Combine batching with rate limit monitoring for optimal throughput
Was this article helpful?