Skip to main content

Pre-Built Tooling

CategoryDetails
AuthenticationOAuth 2.0 (Authorization Code with refresh tokens) + Bearer Token (Basic format)
Two-Way SyncNo
Events SupportedNo
RealtimePolling
Supports Rate LimitingYes
Authentication Scopes Supportedorders (read/write), orders.readonly (read-only), inventory (read/write), inventory.readonly (read-only)

Objects Supported

Alloy Automation supports syncing the following objects from Rithum:
  • Orders
  • Inventory
  • Products
  • Fulfillments
  • Returns

Set Up Guide

Trial Access

QuestionAnswer
Offers free trial?Contact Rithum (formerly ChannelAdvisor) for trial or demo access. Request demo
Requires paid sandbox?Yes. You typically need to work with Rithum to get sandbox environment access.
Requires partnership to obtain authentication?Yes. You need to be a Rithum partner or customer to obtain OAuth credentials.

Authentication (OAuth 2.0)

For customers who want to completely whitelabel their OAuth experience, you can provide your own developer keys instead of using Alloy Automation’s. For API documentation, visit Rithum Developer Portal.

Use Cases

1) Multi-channel inventory management

Sync inventory levels between your warehouse management system and Rithum to maintain accurate stock counts across all sales channels and marketplaces.

2) Order fulfillment automation

Automatically pull orders from Rithum marketplaces to your fulfillment system and sync order status, tracking numbers, and shipping confirmations back to Rithum.

3) Marketplace expansion

Manage product listings, pricing, and inventory across multiple marketplaces (Amazon, eBay, Walmart, etc.) through Rithum’s platform by integrating with your product management system.

4) Returns processing

Automate the returns workflow by syncing return requests from Rithum marketplaces to your returns management system and updating return status back to the marketplaces.

5) Analytics and reporting

Pull order and inventory data from Rithum into your business intelligence platform for cross-channel sales analytics, inventory optimization, and marketplace performance reporting.

API Gotchas

  • Company rebrand: Rithum was formerly known as ChannelAdvisor. API endpoints still use the channeladvisor.com domain. Be aware of this when configuring integrations and reading documentation.
  • OAuth scope requirements: Rithum uses granular OAuth scopes for read and write access to orders and inventory. Plan your scope requirements carefully to avoid needing to re-authorize users later.
  • Bearer format: Despite being OAuth 2.0, the Bearer token uses “Basic” format in some contexts. Follow the API documentation carefully for authentication header formatting.
  • Rate limiting: The API enforces rate limits based on your partnership tier. Implement proper rate limiting and exponential backoff to handle throttling gracefully.
  • Marketplace-specific data: Different marketplaces integrated with Rithum may have different data formats and requirements. Be prepared to handle marketplace-specific fields and validations.
For questions or troubleshooting, contact support@runalloy.com.
I