@ebitex/commerce-sdk
Changes to the Commerce SDK for JavaScript and TypeScript. Newest first. How versions work is on Releases and versions.
2026-11-19 — Checkout
Section titled “2026-11-19 — Checkout”startCheckout() turns a cart into an order awaiting payment and returns the payment provider’s page to send the shopper to. The client refuses a bad email or return address before sending it, with the API’s own codes. See Read a Commerce catalogue from JavaScript.
2026-11-19 — Currencies and carts
Section titled “2026-11-19 — Currencies and carts”A store can sell in several currencies, and a key made with Allow carts and checkout can run a shopper’s cart. store() lists the currencies, a product read takes currency, and the new cart methods create a cart, set a line, the addresses and the promotion codes, read it with every price and total worked out by the server, and delete it. Every cart call takes the shopper’s visitor token, sent as a header. The client refuses locally, with the API’s own codes, what the API would refuse. See Read a Commerce catalogue from JavaScript.
2026-11-19 — Clients for the Commerce Delivery API
Section titled “2026-11-19 — Clients for the Commerce Delivery API”Two new packages read a Commerce store from your code. @ebitex/commerce-sdk works in a browser with a browser-safe key or on a server, with no runtime dependencies: it reads a store’s products, prices, availability and categories, pages through them, reads products by key, and reads live stock. Ebitex.Commerce.Delivery does the same from a .NET server. Both send a cursor back with exactly the query that produced it, report an error with the API’s code and request id, and refuse early what the API would refuse. A browser-safe key is told exact stock counts only when the store allows it. See Read a Commerce catalogue from JavaScript and Read a Commerce catalogue from a .NET server.