Skip to main content

Get Lag Time Summary

GET 

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

Settings, today's lag-time feed budget, ledger counts by status, pending changes by urgency, the earliest time the automatic schedule may send each kind of change, and the last push run.

Not yet available to API tokens

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

Authentication: Requires Bearer token.

Walmart allows 6 lag-time feeds per rolling day; one is always kept for manual pushes. budget.next_slot_at is set only when no slot is free. next_automatic_flush.* is null while the automatic budget is spent or the feature is off.

initial_import says whether Walmart's current lag times have been imported yet (imported_at, plus error when the last attempt failed). While waiting is true nothing is pushed automatically and Push Pending Lag Times is refused, so only real differences are ever sent. settings.importedAt / settings.importError carry the same values and are set by the server only; a settings save never changes them. capabilities.maxChangesPerTransmission is the most SKUs one feed carries (Walmart: 5000); the rest go in the next feed.

counts.held counts pinned lag times that cannot be sent because the listing is archived, unlinked or fulfilled by Walmart. They are not included in counts.pending, pending_urgent or pending_normal, and are sent on the first push after the listing can be sent again.

Approved maximum: SKU.io never sends a lag time above the store's settings.maxApprovedDays (0–10, default 1 — Walmart allows more than 1 day only with an approved lag-time exemption). max_approved_days is that value (within Walmart's 0–10 range) and exemption_required counts listings held at it because they need more.

Request​

Responses​

OK

Response Headers
    Content-Type