We just GoLive API Rate Limits. Please follow up
Products
1. Add new enpoint for Product/Stock/Serial number
2. sale_price replaces price_sale on product & catalogue payloads
sale_price is the documented name for a product's selling price. price_saleis no longer described in this reference.
price_sale next to sale_pricewith the same value, and
POST /product/add still accepts it. It is simply outof the documented contract from now on, so migrate your reads when convenient.
sale_price:sale_price wins. 0 is a validprice, not "unset".
sale_price means different things on different objects — see theField naming: sale_price page under Overview before using it to reconcile.4. Category lookup, and variants[].product_id
GET /api/v2/public/product/category.Returns the
category_id values POST /product/add accepts, as a flatpaginated list. No parameters gives you the root categories; pass
parent_category_id to walk down, or keyword to search.category_id on Add Product is now documented and validated. An id thatmatches no category is rejected with
400 instead of being stored. An inactivecategory is still accepted. It cannot be changed on the Update endpoints — a
value sent there is ignored.
variants[].id is now variants[].product_id. Same value, clearer name: itis an Omisell product id.
id still works and there is no removal date;product_id wins if both are sent.WARNING
product_id is only honoured when it is a variant of the product beingwritten. It used to accept any product id on your account, which meant an id
sent by mistake overwrote an unrelated product's name and price. Such an id is
now ignored and a new variant is created instead.
Modified at 2026-09-02 07:55:36