A small update to the Seller API. You stay on v1: the same /api/seller/v1 URLs, the same API
keys and the same X-Avrix-Api-Version contract date. No route, field or error code is removed
or renamed.
Most of this update adds fields you can use. Four changes can affect a live integration; check them first.
Check these#
1. Send the buyer's country on reserve#
Only if you use hot drops (POST /orders/reserve).
- Before: a reserve without a country was priced for the United States.
- Now: it is refused with
422 SALES_COUNTRY_REQUIRED, as hold already was. Reserve also runs the same checks as hold and POST /orders, so a reserve that commit would refuse is refused at reserve. - What to do: send
countryCodeorintegrationOrderContext.salesCountryCodeon every reserve. If you send bothexpectedUnitPriceCentsandexpectedWholesaleUnitPriceCents, they must be equal, or you get422 EXPECTED_PRICE_CONFLICT.
2. Sell each country in the currency it is priced in#
- Before: an agreement could allow a second currency in a country.
- Now: a country is sold in the one currency it is priced in. A sale in another currency is refused with CURRENCY_NOT_PRICED_FOR_COUNTRY, which names the priced currency. SRP_MISMATCH_FOR_CURRENCY is no longer returned.
- What to do: charge in the
currencyCodeof the price you read for that country.
3. Read sellable before you show a price#
- Before: a price you could read was a price you could sell.
- Now: a price can be listed with
sellable: falseand ablockedReason, for example when the Content Owner does not allow that currency in the country. An order for it is refused. - What to do: hide or disable prices with
sellable: false. This applies to the snapshot'sterritoryPrices[],GET /products/{id}/pricingandGET /products/{id}.
4. Error codes when more than one check fails#
- Before: different order endpoints could name different codes for the same sale.
- Now: every order endpoint names the first failed check in one fixed order. For example, a country you have not declared and that has no price now answers FOOTPRINT_COUNTRY_NOT_DECLARED instead of CATALOG_PRICE_NOT_SET.
- What to do: only if your code branches on specific error codes. The order is listed at the top of the Error reference.
New you can use#
currencyExponentnext to every money amount, including thesku.pricing_updatedwebhook. An amount iscents / 10^currencyExponent: JPY 2480 is 2,480 yen. Amounts themselves did not change. See Money fields.- A price per SKU:
skus[].prices[]onGET /products/{id}andGET /products/{id}/pricing. This is the price a sale charges. - A price on availability:
GET /availability?country=returnspricefor each country. - Price zones: every price carries
zone, for example Steam's Euro zone. fallbackFromCurrency: set when a country is priced in another currency than the one your store charges there.- Partner access: GET /whoami gains
accessByPublisher: the countries and currencies each Content Owner lets you sell, and changes still to come. Content Owners can offer you more countries or currencies; see them with GET /access/proposals and answer with POST /access/proposals/{id}/accept or/decline. - No default country: nothing assumes the United States any more. Readiness checks use the countries you declared.
Still works, but deprecated#
- Release-level prices:
pricing[]onGET /products/{id}andprices[]onGET /products/{id}/pricing. Useskus[].prices[]on the same responses instead. - SRP_MISMATCH_FOR_CURRENCY and
details.floorMinor: no longer returned. Handle CURRENCY_NOT_PRICED_FOR_COUNTRY instead.
Both stay for now. Dates for removal will be on Versioning and compatibility.
All the details#
Each change has its own dated entry in the Changelog, with the full detail. Questions? Ask your Avrix contact.