The Catalog API can return 200 even when some records fail. A 200 means Insider One processed the request, not that every product was accepted. Test with a small batch first.
Check the result in the InOne panel
Go to Components > Catalog Management. If the item is locked, your plan does not include it.
Open Catalog Manager and select the feed type, locale, currency, and time range that match your request. Currency appears only for some feed types.
Select Filters > Item ID and enter one of the product IDs from your request. Insider One accepts valid records and adds them to the catalog asynchronously, so a product may not appear right away. Wait a few minutes and check again.
Check that the name, price, URL, stock values, and Product Activation Status match your request.
Open Catalog Data Validation in the Onboarding Center, under Product Catalog Integration, and check for errors on the products you sent. After you confirm validation, the catalog data is locked.
Interpret a partial success response
Field | Meaning | What to do |
|---|---|---|
success | true when every record is valid. false when even one record is invalid. | Do not rely on the status code alone. Check this field first. |
message.valid.count | Number of records accepted. | Compare with the number of records you sent. |
message.invalid.details[] | Errors grouped by error message. Each item has message, field, count, and document_ids. The response returns at most 10 IDs for each error message. | Fix the field named in the error. If count is higher than the number of IDs in document_ids, fix the field and resend the whole batch. |
message.warnings | Warnings about the request. | Read each warning and fix the cause if it applies to your data. |
Read the response body on every call. A record can fail while the status code stays 200. Valid records are accepted and added to the catalog asynchronously, so a valid record may not appear in the panel right away.
Reproduce a failure in Postman
Open the endpoint page and select Run in Postman. The Insider One Postman documentation opens at that endpoint.
In the top right corner of the Postman documentation, select Run in Postman.
In the Fork collection into your workspace window, select Fork Collection. Postman opens the collection in the Postman app or in your browser.
Select the environment that holds your API key and partner name.
In the Body tab, select raw and paste the payload from your integration.
Select Send and compare message.invalid.details with your integration log.
Reduce the payload to one product, then add products back until the error returns.
Remove the API key before you share the request or response.
To intentionally trigger a known error, send a product without a required field, such as the name or the URL.
For more information, see Insider One APIs in Postman and API Status and Error Codes.