獲取資料處理結果
如果資料狀態顯示為已完成,那麼你就可以通過這個接口獲取處理報表。
相關URL
Newegg.com: https://api.newegg.com/marketplace/datafeedmgmt/feeds/result/{Requestid}?sellerid={sellerid} Neweggbusiness.com: https://api.newegg.com/marketplace/b2b/datafeedmgmt/feeds/result/{Requestid}?sellerid={sellerid} Newegg.ca: https://api.newegg.com/marketplace/can/datafeedmgmt/feeds/result/{Requestid}?sellerid={sellerid}
註:請確保您的請求URL全都是小寫(除Seller ID)並且不能包含任何空格或者分行符號。
參數
名稱 | 是否必填? | 描述 |
sellerid | 是 | 您在新蛋商城的商家編號 |
Requestid | 是 | 已提交的資料請求的請求ID |
相關請求資訊
HTTP方式 | 是否需要認證? | 請求格式 | 回覆格式 | 頻率限制 |
Get | 需要 | XML,Json | XML,Json | 10,000 請求/小時 |
示例:XML, Request
GET https://api.newegg.com/marketplace/datafeedmgmt/feeds/result/{Requestid}?sellerid={sellerid} Authorization: 720ddc067f4d115bd544aff46bc75634 SecretKey: 21EC2020-3AEA-1069-A2DD-08002B30309D Content-Type: application/xml Accept: application/xml
示例:Json, Request
GET https://api.newegg.com/marketplace/datafeedmgmt/feeds/result/{Requestid}?sellerid={sellerid} Authorization: 720ddc067f4d115bd544aff46bc75634 SecretKey: 21EC2020-3AEA-1069-A2DD-08002B30309D Content-Type: application/json Accept: application/json
回覆文件主體
屬性 | 格式 | 描述 |
DocumentVersion | Decimal | 固定值:1.0 |
MessageType | String | ProcessingReport |
OrginalMessageName | String | 標識已處理資訊的有效值 |
OriginalMessageType | String | 可用於標識相關請求類型的錯誤或是警告的適用資訊。 |
ProcessedStamp | Datetime | 已處理資訊的時間標記 時間格式:8/12/2010 9:32:33 PM |
StatusCode | String | 標識資訊處理狀態的有效值 |
ProcessedCount | Integer | 已處理記錄的總數 |
SuccessCount | Integer | 已成功處理記錄的總數 |
WithErrorCount | Integer | 已處理記錄中出錯的記錄總數 |
SubCategoryID | String | 可用於標識相關請求類型的錯誤或是警告的適用資訊。 |
SellerPartNumber | String | |
ManufacturerPartNumberOrISBN | String | |
NeweggItemNumber | String | |
UPC | String | |
OrderNumber | String | |
TrackingNumber | String | |
ErrorDescription | String | 錯誤或警告的原因 |
Schema: ProcessingReport.xsd
示例:XML, Response
<?xml version="1.0" encoding="utf-8"?> <NeweggEnvelope> <Header> <DocumentVersion>1.0</DocumentVersion> </Header> <MessageType>ProcessingReport</MessageType> <Message> <ProcessingReport> <OriginalMessageName>APIAutoFile.xml</OriginalMessageName> <!-- please ignore this element --> <StatusCode>ProcessReport</StatusCode> <ProcessingSummary> <ProcessedCount>3</ProcessedCount> <SuccessCount>1</SuccessCount> <WithErrorCount>2</WithErrorCount> </ProcessingSummary> <Result> <AdditionalInfo> <SubCategoryID>1648</SubCategoryID> <SellerPartNumber>sellerparttest001</SellerPartNumber> <ManufacturerPartNumberOrISBN>mftparttest001</ManufacturerPartNumberOrISBN> <UPC /> </AdditionalInfo> <ErrorList> <ErrorDescription>Error(s). Item not created.</ErrorDescription> <ErrorDescription>Manufacturer - The manufacturer does not exist in our system. Please contact Marketplace Support for more information </ErrorDescription> </ErrorList> </Result> <Result> <AdditionalInfo> <SubCategoryID>1648</SubCategoryID> <SellerPartNumber>sellerparttest002</SellerPartNumber> <ManufacturerPartNumberOrISBN>mftparttest002</ManufacturerPartNumberOrISBN> <UPC>null</UPC> </AdditionalInfo> <ErrorList> <ErrorDescription>Error(s). Item not created.</ErrorDescription> <ErrorDescription>UPC - Format Error: UPC must be an numeric string of at least 12 digits.</ErrorDescription> </ErrorList> </Result> </ProcessingReport> </Message> </NeweggEnvelope>
示例:Json, Response
{ "NeweggEnvelope": { "Header": { "DocumentVersion": "1.0" }, "MessageType": "ProcessingReport", "Message": { "ProcessingReport": { "OriginalMessageName": "APIAutoFile.xml", "StatusCode": "ProcessReport", "ProcessingSummary": { "ProcessedCount": "3", "SuccessCount": "1", "WithErrorCount": "2" }, "Result": [ { "AdditionalInfo": { "SubCategoryID": "1648", "SellerPartNumber": "sellerparttest001", "ManufacturerPartNumberOrISBN": "mftparttest001" }, "ErrorList": { "ErrorDescription": [ "Error(s). Item not created.", "Manufacturer - The manufacturer does not exist in our system. Please contact Marketplace Support for more information." ] } }, { "AdditionalInfo": { "SubCategoryID": "1648", "SellerPartNumber": "sellerparttest002", "ManufacturerPartNumberOrISBN": "mftparttest002", "UPC": "null" }, "ErrorList": { "ErrorDescription": [ "Error(s). Item not created.", "UPC - Format Error: UPC must be an numeric string of at least 12 digits." ] } } ] } } } }
請求失敗錯誤資訊
常規HTTP錯誤回應,請參考回覆失敗錯誤代碼清單。
錯誤代碼 | 描述 |
DF004 | Unfortunately, we are unable to process your request at this time. We apologize for the inconvenience. Please try again later. 抱歉,當前我們無法處理你的請求。我們為給你造成的不便致歉。請稍後再試。 |
DF005 | Your feed was not submitted successfully (Feed Request ID:[{0}]). Please resubmit your feed again. 你的資料沒有提交成功(Feed Request ID:[{0}]).請重新提交你的資料。 |
DF006 | The requestID cannot be null. requestID 不能為空 |
DF007 | Invalid RequestID. 無效的 requestID |
DF010 | Data feed request processing failed:{0} Available values: a. FileContentError (mapped error message:Incorrect data feed format or template) b. No record (mapped error message:request with no record specified.) 資料請求處理失敗:{0} 有效值: a. 文件內容錯誤(匹配錯誤資訊:錯誤的資料格式或範本) b. 沒有記錄(匹配錯誤資訊:請求中無給定記錄) |
示例:XML, Response
<?xml version="1.0" encoding="utf-8"?> <Errors> <Error> <Code>DF006</Code> <Message>Invalid RequestID</Message> </Error> </Errors>
示例:Json, Response
[ { "Code": "DF006", "Message": "Invalid RequestID" } ]
更新日期:10/15/2018