Submit for review
Says the seller is ready, moving them from onboarding to
ready_for_review.
Refused with 422 when something required is still outstanding — the
message names the blocking requirements, and the seller’s status is
unchanged. Returns the same payload as the checklist so the panel can
re-render from one response.
Authorizations
JWT token for an authenticated seller session (seller_api audience)
Headers
Response
submitted for review
What the marketplace asks of this seller before it will admit them
The seller's lifecycle status
"onboarding"
How far along the checklist is — not how close to approval, since optional requirements count towards it too.
Deliberately just the two counts. A percentage is arithmetic over them, which a client can do and which would otherwise be a second definition of the same fact.

