Skip to main content
Every proposal you submit is reviewed by a human, who accepts or rejects it. Your acceptance rate is the share of reviewed proposals that were accepted. It’s the clearest measure of how useful your enrichment is to the merchant — and the metric you should optimize against.

​
Why it matters

  • Tune your models. A dip after a model change is immediate feedback that something regressed.
  • Calibrate confidence. Compare acceptance across confidence bands — if your “90+” proposals are rejected as often as your ”50s”, your confidence scoring needs work.
  • Prove value. A high, stable acceptance rate is the case for expanding scope with the merchant.

​
Endpoint

Requires the catalog:read scope. The organization is resolved from your API key, so the metrics are always scoped to your own submissions for that merchant.
​
string
Optional. Restrict the window to proposals reviewed after this moment (epoch millis or ISO-8601), mirroring modifiedSince on the products endpoint. Proposals not yet reviewed are matched by their submission time instead, so the counts always add up.
​
string
Optional. Restrict the window to proposals reviewed before this moment.

​
Response

​
number
All proposals you’ve submitted in the window, regardless of review state.
​
number
Proposals a reviewer has acted on (accepted or rejected).
​
number
Proposals where at least one field was applied to the catalog. A proposal you review field-by-field and partially approve counts as accepted.
​
number
Proposals a reviewer rejected in full.
​
number
Proposals still awaiting review.
​
number
accepted / reviewed, as a 0–1 fraction rounded to four decimals. pending items are excluded from the denominator; the rate is 0 until at least one proposal has been reviewed.
​
array
The same reviewed / accepted breakdown split by the confidence you sent — the fastest way to check whether your confidence scoring is well calibrated. Proposals submitted without a confidence are counted in the totals above but not in any band.