List Account Anomalies
GET/api/product-account-map/anomalies
Products whose account for one type differs from at least 80% of the other active products in their primary category (categories with 5 or more active products). Anomalies are a prompt to check, never a block. Dismissed anomalies are left out until the product moves to a different account.
accounting:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token with the accounting:read scope.
Row fields: product_id, sku, name, category ({id, name}), account_type, account ({id, code, name, archived_at}), source (rule, product_override, company_default or unmapped), category_majority ({account, count, total} — the category's usual account and how many of its products use it), rule_would_apply (a rule sets this type for the product, so clearing its override would hand it to the rule), rule ({id, name} of that rule, or null).
Standard paginated response; default 10 per page (max 500).
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.