Skip to main content

List Lag Times

GET 
/api/walmart/:integrationInstance/lag-times

List the per-listing lag-time ledger for a Walmart integration: what SKU.io wants Walmart to promise (desired_days), what Walmart has confirmed (pushed_days), and why.

Not yet available to API tokens

This endpoint currently requires session authentication; Personal Access Token scope support is in progress.

Authentication: Requires Bearer token.

Filters: search (channel SKU, product SKU or listing title), mode, push_status (comma-separated for several), urgency, pending (true = desired differs from pushed), product_listing_id. Sorts: id, channel_sku, desired_days, pushed_days, pushed_at, push_status, updated_at, mode. Default: -id. Pagination: page, per_page (default 10).

mode: baseline | automatic | pinned. push_status: pending | submitted | confirmed | failed | refused (Walmart refused a value the item may not have, e.g. above 1 day without a lag-time exemption). pushed_source: sku_io | channel_report. effective_days = pushed_days, else desired_days.

Operator-aware filters: every filterable column also accepts filter[<column>.<operator>] (e.g. filter[desired_days.greater_than]=1) and the base64 filter_groups tree for AND/OR combinations. filter[mode], filter[push_status] and filter[urgency] accept a comma-separated list.

is_held is true for a pinned lag time waiting to be sent whose listing currently cannot be sent (archived, unlinked or fulfilled by Walmart).

rule is desired_reason.rule. is_exemption_required is true (rule exemption_required) for a listing held at the store's approved maximum because it needs more: desired_days is the maximum, refused_days is what it needs, and nothing above the maximum is ever sent. Such a listing reads push_status refused once Walmart holds the maximum.

Request​

Responses​

OK

Response Headers
    Content-Type