Dismiss Account Anomaly
POST/api/product-account-map/anomalies/dismiss
Keep a product's unusual account: the anomaly is dismissed against the product's current account for that type. If the product later moves to a different account, the anomaly can be raised again.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token with the accounting:write scope and the manage-accounting-settings permission.
Request body fields:
product_id(integer, required) — an existing product.account_type(string, required) — sales, cogs, inventory, inventory_in_transit, accrued_purchases or discount.
Returns 422 when the product has no account for that type.
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.