Skip to main content

Public API - name every unlisted product and its line in the quote-create error

Feature Request

What is the problem, wish or change?
When an integration creates a quote with an unlisted product, the Public API answers 400 "Product is unlisted" without saying which product. It also stops at the first one it finds, so an integration has to fix and resend the request line by line.
Who or what is impacted?
Integrations that create quotes through the Public API (raised by GOsensit), and support staff who debug their failed calls.
Why does this matter now?
The other quote-create errors already name the product (unknown product, missing pricing). This one is the outlier, and it costs integrators a separate check per line.
What does "done" look like?
A quote-create request containing unlisted products is rejected once, with an error that lists every unlisted product and the position of its line in the request.
Acceptance criteria:

  • The 400 response names every unlisted product in the request, with its product id and line position.

  • A request with several unlisted products gets one response that lists all of them.

  • Adding a product to an existing quote through the API reports an unlisted product in the same format.

  • Requests without unlisted products behave exactly as today.

  • The error format is documented in the Public API docs.

1 comment

Log in to comment and vote

Comments1

  • Bram Fofana

    Team•

    Nov 4

    The other quote-create errors already name the product, so the unlisted-product error being the exception that stops at the first line is inconsistent. I am taking this to refinement: one response that lists every unlisted product with its id and line position, for quote create and for adding to an existing quote. No timeline yet.