Use this file to discover all available pages before exploring further.
The backfill counterpart to single-record upsert. Send up to 1,000 user records in one POST; per-record validation errors are surfaced in the response, the rest are queued.
SDK is the recommended path.vf.users.identifyBulk() wraps this endpoint with strong typing and pairs cleanly with the exported chunk() helper for backfills larger than 1,000 records.
Total records in the request payload. accepted + rejected === meta.received is an invariant — every record is accounted for.
Idempotency is automatic. The (project_id, external_user_id) uniqueness constraint on tracked_users means re-sending the same record with the same external_user_id is treated as an update, not a duplicate. Any chunk that returns 429 or 5xx is safe to retry.
import { VibeFollow, chunk } from '@vibefollow/sdk';const vf = new VibeFollow({ apiKey: process.env.VIBEFOLLOW_API_KEY! });// Backfill any size by pairing with chunk()for (const slice of chunk(allUsers, 1000)) { const result = await vf.users.identifyBulk(slice); if (result.data.errors.length > 0) { console.warn('skipped', result.data.errors); }}
The envelope failed validation — users is missing, not an array, empty, or contains more than 1,000 records. Per-record validation failures do not trigger 400; they surface in data.errors.
429 rate_limited
Standard per-project rate limit; honor Retry-After.
429 backfill_queue_full
The project’s ingest queue is saturated (50,000+ jobs waiting or delayed). Back off, drain, then resume in smaller chunks.
5xx server_error
Retry the same chunk — the upsert is idempotent via the unique (project_id, external_user_id) constraint.