Skip to main content

Stocks

Format for sending stock updates to locations. A single call can contain updates for multiple locations.

The location_id corresponds to the Channel Engine location ID, which can be found on the Stock locations page. In the table, the first column ID indicates the location where the stock should be updated.

If there is only one location, you can configure it directly in the request header, avoiding specifying it in every message. The quantity (qty) must always be provided and cannot be negative, while the SKU (sku) is required for each update.

[
{
"sku": "BGSM001C210A-1",
"qty": 34,
"location_id": 10
},
{
"sku": "BGSM001C210A-2",
"qty": 35,
"location_id": 4
}
]

Destination configuration

Configure a Channel Engine destination and associate it with the flow, in addition to the basic data flow configuration.

FieldValueNotes
Destination TypeChannel Engine
OperationStock syncPOST /egress/sync-stock-to-ce
Channel Engine URLhttps://CEURL.channelengine.net/apiChannel Engine API base URL
Channel Engine tokenALPHANUMERICCODEChannel Engine API token
Location IDe.g. 123Optional Channel Engine location id

Deprecated — previous configuration (HTTP Adapter)

Deprecated

Configuration via HTTP Adapter with Base Url, Resource Path, and x-api-key header in Settings Override is deprecated. Use the Channel Engine destination configuration described above.

In addition to the basic data flow configuration, the following Settings Override settings were required:

FieldValueNotes
Base Urlhttps://adapter.flowlyze.ioURL of the adapters
Resource Path/api/adp/channel-engine/egress/sync-stock-to-ceAdapter path for stock updates
Headers :: x-api-key**********API key used to validate endpoint interaction
Headers :: x-ce-urlhttps://CEURL.channelengine.net/apiURL of the Channel Engine to connect to
Headers :: x-ce-tokenALPHANUMERICCODEToken for the integration
Headers :: x-ce-location-idlocationIDDefault location id for each call