Check whether bulk classification can run
Report whether POST /products/bulk-classify is worth running, across every organization your credential owns; send an Organization-Id, Connection-Id or Entity-Id selector to narrow to one. canClassify is true only when totalProducts meets minProducts and at least one product needs classification work: pending, or a status POST /products/bulk-classify would reset and re-run.
Authorization
Headers
Release date, as YYYY-MM-DD. Defaults to 2026-07-21.
Narrow the request to one organization (Organization-Id selector).
Narrow the request to a connection's organization.
Narrow the request to a platform entity's organization.
Optional source to disambiguate an Entity-Id.
Query
Every query parameter below is optional. Combine as many as you need and append them to the endpoint as a query string. The example shows a few to get you started.
/products/classification-status?minProducts=<minProducts>Minimum product count required for canClassify to be true.
Response
Whether POST /products/bulk-classify is worth running: enough products exist and at least one needs classification work, meaning it is pending or is a status bulk-classify would reset and re-run (partially approved or previously failed classification).
Product count across the resolved organizations.
Whether any resolved organization has a product in PENDING status.
The product count totalProducts must meet for canClassify to be true.
Successful Response
The request was invalid.
Authentication failed or was missing.
The credential is not permitted for this request.
The requested resource was not found.
The request conflicts with existing state.
The request failed validation.