client.vendor.pushOffers()
Upsert up to 500 listings keyed by your own SKU. Ids we do not hold come back as unmatched rather than failing the batch; a bad row (a string price, a float) is a 400 with details naming it.
pushOffers(input: PushOffersInput, scope?: VendorScope): Promise<APIResponse<PushOffersResult>>- stringheaderrequired
Your API key.
Authorization: Bearer <key>is accepted in its place.
- string
Which of your shops to act for. Required only when one key is named by more than one shop;
GET /v1/vendor/shopslists them- Max length
- 64
- Example
- object[]required
The listings to upsert, keyed by your own SKU. Up to 500 per request.
- object
The response payload.
- integer
Offers accepted and stored.
- object[]
Rows naming a record we do not hold. Reported rather than failing the batch, so a mapping error is a review and not a rejected push.
- string
The shop's own catalogue key for the listing. A seller's identifier, not ours: it is what
PATCH /v1/vendor/offers/{sku}addresses. - OfferTargetKind
What a seller listing is for.
- string
The id the row named, which we do not hold.
- 400
VALIDATION_ERROR - 401
UNAUTHORIZED - 403
FORBIDDEN - 413
PAYLOAD_TOO_LARGE - 429
RATE_LIMITED - 500
INTERNAL_ERROR
- Minimum tier
- Enterprise
- Monthly quota
- 1,000,000/mo
- Rate limit
- 300/min
- Daily cap
- 50,000
Figures shown are for this endpoint's minimum tier. Higher tiers raise every limit.