POST Feed File: How to Upload Feed Files
All feed files are uploaded using Walmart's Feed APIs (POST /v3/feeds
), but each distinct feed file must be identified using the query parameter (feedType=
). The user must include the load file.
Note: The requestor must ensure the
feedType
(defined in the query parameter) and the load file must match.
The following sections provide an example of a user setting up items using Feed APIs.
Example Request
The user provides the sample request and file defined in the body.
Example:
POST https://api-gateway.walmart.com/v3/feeds?feedType=OMNI_DSV_ITEM.
{"file": "c:\input\feedfiles\OMNI_DSV_Item23456.json"}
Note: File extensions will only be accepted if they end with
.json
or.xml
. File extensions must match the supported feed file format.
After a supplier submits a feed, the supplier will only receive a response if the file is accepted. Otherwise, the request will result in an error.
Response Body for Successful Submission
The returned value for all successful feed submissions is the feed ID (feedId
).
Example:
{"feedId":2D4DB32BC1174C7491720C9EBEB56163@AQMBAAA}
The feed ID (feedId
) is used to track the continuing status of the request. All feeds are processed asynchronously (async), so suppliers must continue monitoring the feed file after submission. Use this monitoring to identify if Walmart systems successfully processed the submission.
Response Body for Failed Submission
The following example is the response body for failed submissions.
Example:
{ "error": [ { "code": "INVALID_REQUEST_PARAM.GMP_DATA_STATUS_API", "field": "feedType", "info": "One or more request parameters are invalid.", "severity": "ERROR", "category": "DATA", "causes": [] } ]
}
Updated about 2 months ago