What It Does
The Bulk Updates API lets you submit large-scale product attribute changes as a background job. Items are processed in batches with per-item error isolation — a single failing row does not abort the entire job.Typical Flow
- Create job — submit a list of product patches via
create_bulk_update_job. - Check progress — poll job status via
get_bulk_update_job. - Inspect items — retrieve per-item outcomes via
list_bulk_update_job_items.
Authentication & Permissions
All RPCs require an authenticated session. Mutations require a role with sufficient permissions for the target brand.RPCs
create_bulk_update_job
Creates a new bulk update job with one or more product patches. Request- Not authenticated — request has no valid JWT.
- Forbidden — caller does not have sufficient access.
- Invalid input — request is malformed or cannot be processed.
- Idempotency is supported: submitting the same
_idempotency_keytwice returns the existing job. - Only one job per brand is typically active at a time.
get_bulk_update_job
Returns the current state of a single bulk update job. Request- Not authenticated — request has no valid JWT.
- Forbidden — caller does not have sufficient access.
- Invalid input — request is malformed or cannot be processed.
list_bulk_update_jobs
Lists bulk update jobs for a brand, ordered by creation date (newest first). Request- Not authenticated — request has no valid JWT.
- Forbidden — caller does not have sufficient access.
- Invalid input — request is malformed or cannot be processed.
list_bulk_update_job_items
Returns individual item outcomes for a job, with pagination. Request- Not authenticated — request has no valid JWT.
- Forbidden — caller does not have sufficient access.
- Invalid input — request is malformed or cannot be processed.
- Items that fail after 3 attempts are marked as permanently failed.