Rithum / Channel Advisor
Description
Rithum (formerly ChannelAdvisor) is an e-commerce channel management platform that lets brands and retailers list, sell and fulfill products across marketplaces such as Amazon, Walmart and eBay.
Setup guide
Follow our setup guide to connect Rithum / Channel Advisor to Improvado.
By default the connection uses Improvado’s own Rithum application, so you do not need a ChannelAdvisor developer account, a developer application, or an agreement with Rithum — you sign in and approve access. If your organisation prefers to keep the application under its own developer account, the other two options below let you do that.
Click the Connections in the left navigation bar.
Categories on the Data sources page group all available platforms. Use a search to find the required one.
Click on the Rithum / Channel Advisor tile.
Choose authorization option:
Use this option unless you specifically need the application to belong to your own developer account. Nothing has to be created in ChannelAdvisor first. Enter a Connection Name. One connection covers every ChannelAdvisor profile the authorizing user can reach, so name it after your organisation rather than after a single profile. Choose the access level. Read Only is the default and is enough for every report Improvado extracts. Choose Read & Write only if you also want the Improvado AI Agent to act back in ChannelAdvisor on your behalf — a granted authorization keeps the access it was issued with, so widening it later means reconnecting. Click Authorize and sign in to ChannelAdvisor. The person who signs in must be a Brands Platform user with Group Admin permissions — ChannelAdvisor does not let other users grant API access.Authorize with Improvado (default)
Use this option when the application has to stay under your organisation’s developer account. It requires access to the ChannelAdvisor Developer Console. In the ChannelAdvisor Developer Console, open your application and copy its Application ID and Shared Secret — the official Generate Developer Console tokens article walks through creating the application. Enter them as Client ID and Client Secret. Your application’s Redirect URI must exactly match the one Improvado sends you back to, or ChannelAdvisor will refuse the sign-in. Contact Improvado support for the value that applies to your account. Click Authorize and complete the ChannelAdvisor sign-in, again as a Group Admin. Improvado receives and stores the tokens for you.Your own ChannelAdvisor application
Use this option when your own application already has a refresh token you want to reuse. In the ChannelAdvisor Developer Console, open your application and copy its Application ID and Shared Secret, then generate a refresh token. The official Generate Developer Console tokens article walks through creating the application and issuing the token. Copy the refresh token when it is shown — Rithum does not display it again afterwards. Fill in the connection form — Client ID is the Application ID, Client Secret is the Shared Secret, and Refresh Token is the token issued for that application.Existing Refresh Token
After the connection is completed, the Rithum / Channel Advisor connection will appear in your Connected sources list under the name you gave it.
When the connection status is Active, and the account status column shows a number of accounts, you can move on to data extraction. Each ChannelAdvisor profile the authorization can reach becomes one account.
To extract data from the connected sources, check the instruction on how to set up data extraction.
Schema information
The schema information shows all report types you can use to extract data from Rithum / Channel Advisor.
Limits
Access tokens issued by Rithum expire after one hour. Improvado refreshes them automatically, so no manual action is needed after the connection is made.
Orders are extracted per ChannelAdvisor profile and are re-fetched by their last update time, so status changes on older orders are picked up.
Release notes
Rithum documents the API and its OAuth flow in the ChannelAdvisor API knowledge base.
Was this article helpful?
Thanks for the feedback!