Get lag time for an item

Use the Lag Time GET endpoint to return the current fulfillment lag time for a single item. Lag time is the number of days between when an item is ordered and when it is shipped. Use this endpoint to:

  • Look up the lag time configured for a specific item to validate recent changes or audit exceptions.

Prerequisites

Complete the following before you start integration LagTime API:

  • Create a seller account on Walmart Marketplace.
  • Get your API credentials.

Best practices

  • Keep lag time at 0 or 1 day. Request approval before using 2 days or more.
  • After posting a bulk update feed, verify a sample of SKUs with this GET endpoint.

Endpoint

GET https://marketplace.walmartapis.com/v3/lagtime

Query parameters

Provide one product identifier. If your program uses ship nodes, include the ship node.

  • sku (string). SKU of the item. Required if gtin is not provided.
  • gtin (string). GTIN of the item. Required if sku is not provided.

Required headers

  • WM_SEC.ACCESS_TOKEN. OAuth 2.0 access token.
  • WM_QOS.CORRELATION_ID. Unique ID you generate per request.
  • WM_CONSUMER.CHANNEL.TYPE (optional). Used by some integrations.

Request and response

Sample request

curl --location 'https://marketplace.walmartapis.com/v3/lagtime?sku=ABC-123' --header 'WM_QOS.CORRELATION_ID: 3b86f6a8-2f5b-4b1a-9b4b-0c7e3b5b9a10' --header 'WM_SEC.ACCESS_TOKEN: <access_token>' --header 'Accept: application/json'

Modify your code

  1. Replace ABC-123 in sku=ABC-123 with your SKU. To query by GTIN instead, use ?gtin=<your_gtin> and remove sku.

  2. If your catalog uses multiple ship nodes, add &shipNode=<your_ship_node_id> to the query.

  3. Replace <access_token> with a valid OAuth 2.0 access token in the WM_SEC.ACCESS_TOKEN header.

  4. Generate a new unique value for WM_QOS.CORRELATION_ID for every request.

  5. Keep Accept: application/json. Add WM_SVC.NAME and WM_CONSUMER.CHANNEL.TYPE if your integration requires them.

  6. Parse the 200 response and read fulfillmentLagTime. If you receive 401, refresh the token and retry.

Sample response

{ "sku": "ABC-123", "gtin": "00012345678905", "fulfillmentLagTime": 2
}

Result

The response includes the item identifier you queried and the fulfillmentLagTime value in days.

How it works

  1. Get an OAuth 2.0 access token with the Token API. Use the token in the WM_SEC.ACCESS_TOKEN header.
  2. Call GET /v3/lagtime with either sku or gtin. If your program uses ship nodes, include shipNode.
  3. Read fulfillmentLagTime from the response. If the value is 2 days or more, make sure your account has the required approval.

Troubleshooting

  • 401 Unauthorized. The access token is missing or expired. Get a new token and retry.
  • Item not found or mismatched ship node. Confirm the identifier you sent and, if applicable, the correct shipNode.

Next steps

  • Update lag time in bulk. POST /v3/feeds with feedType=lagtime to update many items, then re-check with GET /v3/lagtime.