Sales Channel Services API v2.1.0
· One min read
This release only features technical improvements under the hood.
No new features or behavioural changes to the API have been introduced in this release.
This release only features technical improvements under the hood.
No new features or behavioural changes to the API have been introduced in this release.
POST /saleschannel-services/traders/{traderId}/inventory/retire
-endpoint, such that it requires the retirementPurpose
, beneficiaryName
, and beneficiaryLocation
-field exclude certain characters which would fail the retirement to be registered, to exclude certain characters, such as +#$^={}|`"<>~
, hexadecimals prefixed with 0x
and emojis.POST /saleschannel-services/traders/{traderId}/inventory/retire
-endpoint, such that it requires the retirementPurpose
, beneficiaryName
, and beneficiaryLocation
-field exclude usage of the *
character in addition to the existing excluded characters, such as +#$^*={}|`"<>~
, hexadecimals prefixed with 0x
and emojis.POST /saleschannel-services/traders/{traderId}/inventory/retire
-endpoint, such that it requires the retirementPurpose
-field to have a length of at least 1 character.salesChannelId
field from Events returned by GET /saleschannel-services/events
-endpointGET /saleschannel-services/events
-endpoint, which together enable paginating on this endpoint.POST /saleschannel-services/traders/{traderId}/inventory/trade
-endpoint, which would allow non-numerical bundle-ranges to be specified, which would prevent being able to read these transactions registration attempts.POST /saleschannel-services/traders/{traderId}/inventory/retire
-endpoint, which would allow non-numerical bundle-ranges to be specified, which would prevent being able to read these transaction registration attempts.GET /saleschannel-services/events
, which can be used to track transaction status change events. Adding more event types, such as inventory changes, are planned.PATCH /saleschannel-services/traders/{traderId}
-endpoint, which would return a HTTP 500.GET /saleschannel-services/production-facilities/{productionFacilityId}
-endpoint, which would return an HTTP 500 response when no Production Facility with the given ID would exist. Now instead, the endpoint will return an HTTP 404 response.This release only features technical improvements under the hood.
No new features or behavioural changes to the API have been introduced in this release.