Add up to 100 lines at once

post

https://apis.kentro.live/store/v1/cart.addMany

Adds up to 100 lines in one revision (a quick-order form, a reorder), each through the cart rules, and answers the cart with a result per line (batch.results: added, adjusted or refused, and why). Idempotent per idempotencyKey: the same key and lines never add twice (batch.replayed). Send expectedUnitPrice on a line to learn whether its price changed.

Who may call it: A guest (X-Storefront-Guest), or a signed-in buyer (X-Storefront-Buyer) whose account is confirmed; an unconfirmed buyer is refused with 403 CONFIRMATION_REQUIRED.

Revision. Send expectedRevision, the revision of the cart you last received (cart.get or the previous write). The cart is written only when it still matches; otherwise the answer is 409 and you reload the cart before retrying. ownershipVersion, from the cart, pins the cart a guest or a claim acts on. A successful write answers the whole cart with its new revision.

Headers

X-Storefront-Host

string

required

length between 1 and 253

The published storefront host the request serves (shop.example.com, lower case). It must belong to the tenant of the API key; 404 NOT_FOUND when no published storefront answers it, 403 FORBIDDEN when it belongs to another account.

X-Storefront-Buyer

string

The signed-in buyer's access token (accessToken from POST https://apis.kentro.live/auth/login/customer). Absent for a guest or an anonymous visitor.

X-Storefront-Guest

string

The guest token session.guest answered, which identifies a guest cart and a guest checkout. Send it along with X-Storefront-Buyer at sign-in so the buyer can choose between the guest cart and the account cart.

X-Storefront-Client-Ip

string

The end buyer's IP address as your storefront server saw it. Used for per-visitor limits (search typeahead, sign-up); without it the limits apply to your server.

X-Expected-Portal

string

The store id (store.get answers id) your page was rendered for. When the host now resolves to another store the answer is 409 CONFLICT, so a stale page never acts on the wrong store.

X-Expected-Buyer

string

The identity your page was rendered for: the buyer id, guest:<guestId> for a guest, or guest for an anonymous visitor. A mismatch with the tokens sent is 409 CONFLICT, so a stale page never acts for the wrong buyer.

Responses

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The cart after the change, with the result per line.

defaultThe request was refused or could not be completed; the status says why (400 validation, 401 sign-in needed, 403 not allowed, 404 unknown, 409 stale revision or version, 422 commerce rule, 429 too many, 503 unavailable).