Get Product API v202309: New not_submitted_reasons Response Field Added

The Get Product API adds a new response field, audit.not_submitted_reasons, to explain why a product has not been submitted for TikTok Shop audit when the shop has not met one or more listing prerequisites. This field is applicable only when audit.status is NONE and unmet shop prerequisites prevent the product from being submitted for audit. In all other cases, the API returns an empty array.

The following response field is added to the Get Product API. Endpoint:GET /product/202309/products/{product_id}

Possible values

Response example

{
  "code": 0,
  "message": "Success",
  "request_id": "your_request_id",
  "data": {
    "id": "1729592969712207008",
    "audit": {
      "status": "NONE",
      "not_submitted_reasons": [
        "SHOP_INACTIVE"
      ]
    }
  }
}

If your app uses the Get Product API, review the following update. Recommended actions:

• Add audit.not_submitted_reasons as an array of strings to your Get Product response model, especially if your app uses strict response deserialization.
• Read this field when audit.status is NONE to identify unmet shop listing prerequisites that block audit submission.
• Support multiple reason values in the array rather than assuming that only one reason will be returned.
• Treat an empty array as no applicable unmet shop prerequisite returned by this field. Continue to use audit.status as the source of truth for the product's audit status.
• Handle unknown future reason values gracefully so that newly introduced values do not cause response parsing failures.
• For US shops, handle W8_NOT_CONFIGURED and guide sellers to provide the required W-8 tax information.
• Test the updated response parsing logic in API Testing Tool before rolling it out to production traffic.

This is an additive response change. Apps that ignore unknown response fields are not expected to require code changes, while apps with strict response schemas should update their models before the field is rolled out.