Channel Engine

The adapters for Channel Engine allow you to easily connect with the platform.

Benefits of our solution:

⚡ Excellent performance for sending data to Channel Engine.

💸 Integrating Channel Engine can be complex. Instead, you can focus on product data with our simplified APIs.

✅ Any changes in the API format or future updates are handled transparently.

💣 Simple JSON for complex operations.

Destination

Configuration of a Channel Engine destination, which will then be used by other flows for interaction with the platform. Download example destination

The configuration form includes the following fields.

Field	Value	Notes
`Destination Type`	Channel Engine	Native Channel Engine destination type
`Operation`	e.g. Product sync	Operation to run on Channel Engine. The value depends on the flow and is documented on the dedicated page. Required field.
`Channel Engine URL`	https://CEURL.channelengine.net/api	Channel Engine API base URL
`Channel Engine token`	ALPHANUMERICCODE	Channel Engine API token

Operation

For egress operations, each selectable value maps to a path under https://adapter.flowlyze.io/api/adp/channel-engine/.

Deprecated

Destination configuration via HTTP Adapter with Base Url and headers in Settings Override is deprecated.

Field	Value	Notes
`destination_type`	HTTP Adapter	Integration adapters worked over HTTP
`Base Url`	https://adapter.flowlyze.io	URL of the adapters
`Headers` :: `x-api-key`	**********	API key used to validate endpoint interaction
`Headers` :: `x-ce-url`	https://CEURL.channelengine.net/api	URL of the Channel Engine to connect to
`Headers` :: `x-ce-token`	ALPHANUMERICCODE	Token for the integration