Submit against a requirement
What the seller says about one requirement: an attestation they tick, a document they upload, a reference they paste.
Create only. A submission records what was said and when, so a seller who needs to correct something submits again rather than editing, and the latest one counts.
file is not a multipart upload — it is the signed_id returned by
POST /api/v3/seller/direct_uploads, so the bytes are already in storage
by the time this runs.
An attestation is accepted on the spot; a requirement the operator
reviews comes back pending.
Authorizations
JWT token for an authenticated seller session (seller_api audience)
Headers
Path Parameters
Requirement ID, as returned by GET /api/v3/seller/onboarding
Body
Response
submission recorded
The values listed are the built-in ones; extensions may add more.
pending, accepted, rejected, waived 
