Skip to content
Last updated

Bulk operations

Bulk work, such as imports, bulk skip trace submissions, scheduled exports and SiftMap auto-add snapshots, runs as activities: background jobs processed through a shared queue. Activities are built for bulk volumes, not for editing a few records.

Limits

GuidelineValue
Minimum records per activity20
Chunk size for large volumes1,000 records per activity
Activity creation rate2-3 per minute per account, any job type
Parallel submissionDoesn't make jobs finish faster (see below)

Rules

  • Don't create an activity to change a handful of records. A job with fewer than about 20 records doesn't get resources allocated properly, and doing it repeatedly is treated as abuse.
  • Use the per-record endpoints for small changes. To change a few records (add a tag, set a status, update a custom field), call the record endpoints directly, for example PATCH /api/internal/property/{uuid}/, POST .../add-tags/ or POST .../add-lists/.
  • Respect the creation rate. Create no more than 2-3 activities per minute per account, whatever the job type.
  • Chunk large volumes. Split large record sets into activities of about 1,000 records instead of one huge job.
  • Parallel submission doesn't help. Activities run through an internal queue, so total throughput is set by the queue, not by how many jobs you submit. Submitting faster than 2-3 per minute gives no speed benefit and may be flagged as abuse.

Track progress

Watch activities in the account activity feed instead of polling records:

  • GET /api/internal/activity/ lists recent activities and their status.

See Activity and reporting.

Choosing between per-record calls and an activity

Records to changeUse
Fewer than 20Per-record endpoints, paced within the rate limits
20 to 1,000One activity
More than 1,000Activities of about 1,000 records, no more than 2-3 per minute