We just GoLive API Rate Limits. Please follow up
Field naming: sale_price
Field naming: sale_price
sale_price is the name this API uses for a selling price. It appears onseveral objects, and the objects do not all mean the same number — the
object you read it from decides which figure you get.
sale_price in a reconciliation.| Where | What the number is |
|---|---|
product (Get Product List / Detail, Add Product) | Retail selling price (RSP) of the inventory product in your Omisell catalogue. |
catalogue (Get Catalogue List / Detail) | Selling price of the listing on the sales channel. Falls back to price when unset. |
items[] of Add Order, Update Order, Get Shipment Detail | Unit price before discount. |
parcels[].items[] of Get Order Catalogues Detail | Price after seller promotion — seller voucher, platform subsidy and platform voucher already excluded. |
parcels[].inventory_items[] of Get Order Detail | Net merchandise value (NMV) of one unit — the net figure Omisell reconciles revenue on, not a listed price. |
WARNING
parcels[].items[] and parcels[].inventory_items[] sit one level apart insidethe same Get Order Detail response, carry the same field name, and mean
different things. If you are matching revenue, read the row above that matches
the exact object you are iterating.
price_sale is replaced by sale_price
price_sale, while orderpayloads already called it
sale_price — two names for one concept in one API.sale_price is the only name documented now. Use it.sale_price. Responses still carry price_sale alongsideit, with the same value, so nothing breaks while you migrate — but it is no
longer part of the documented contract and you should not build on it.
POST /product/add): send sale_price. price_sale is stillaccepted; if you send both,
sale_price wins.WARNING
200with no price set, not an error. Send exactly one of the two spellings.
Not affected
GET /agency/product* and the catalogue webhook payload are a separate payloadshape and are unchanged.
Modified at 2026-09-02 07:55:36