Bulk item operations

Item feeds process create, update, delete, list, and delist tasks asynchronously. A task can fail without rolling back other successful tasks.

Request shapes

Feed type	Input
CREATE	items, using the synchronous create-item request structure
UPDATE	items, each containing item_id plus synchronous update fields
DELETE	item_ids
LIST	item_ids
DELIST	item_ids

IDs must be unique inside a feed. Do not send item_ids for create or update, and do not send items for delete, list, or delist. The maximum accepted task count is configurable; the default service limit is documented in the API reference.

Processing sequence

1. Submit POST /api/public/v1/item-feeds.
2. Store the returned feed_id.
3. Poll GET /api/public/v1/item-feeds/{feedId} until status is FINISHED, or wait for item_feed.finished.
4. Compare success_count, pending_count, and error_count with total_count.
5. If there are errors, page through GET /api/public/v1/item-feeds/{feedId}/tasks and inspect each task's error_message.

Feed states:

State	Meaning
QUEUED	Accepted; tasks have not started
IN_PROGRESS	At least one task is being processed
FINISHED	Every task is either SUCCESS or ERROR

Task states are QUEUED, IN_PROGRESS, SUCCESS, and ERROR.

Feeds are visible only to the API key that created them. Another key belonging to the same collector cannot retrieve the feed or its tasks.