Radial API
REST APIs documented at docs.radial.com span orders, inventory, payments, returns, subscriptions, and fraud and tax services, with push webhooks configured in the Customer Portal. No public OpenAPI spec is published, and webhook callbacks rely on Basic Auth plus IP allowlisting.
Frequently asked questions
Radial scores C on Supergood's API Report Card. REST APIs documented at docs.radial.com span orders, inventory, payments, returns, subscriptions, and fraud and tax services, with push webhooks configured in the Customer Portal. No public OpenAPI spec is published, and webhook callbacks rely on Basic Auth plus IP allowlisting.
Radial has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Radial is an enterprise third-party logistics (3PL) and commerce technology provider that combines an owned-and-operated network of 30+ fulfillment centers across North America and Europe with a software stack covering order management, payment processing, fraud prevention, tax compliance, returns management, and store/dropship fulfillment.
Primary vertical: Fleet / Trucking / Logistics, specifically the enterprise ecommerce fulfillment / outsourced-3PL segment serving mid-market and Fortune 500 brands. An enterprise retailer integrates Radial into its order management and storefront stack, either through a pre-built connector (Shopify, Adobe Commerce/Magento, Salesforce Commerce Cloud, NetSuite), the Radial REST APIs, or EDI, and ships inventory into one or more Radial fulfillment centers (often FTZ-enabled for duty deferral on imported goods).
High inside the enterprise 3PL niche. Radial is one of the most-recognized enterprise fulfillment partners in North America, ships 18M+ units during peak, operates 30+ fulfillment centers, and was acquired by bpost for $820M in 2017.
For merchants on Radial, the API and Customer Portal are the system of record for order routing and fulfillment status across DCs, inventory by SKU and by location, payment authorization and settlement, fraud disposition (approve/decline/review), tax calculation, returns lifecycle, and monthly fulfillment + payments + fraud + tax invoicing, all of which feed directly into storefront accuracy, customer service tickets, marketplace SLA compliance, retailer chargeback exposure, and revenue recognition.
Radial's lineage traces back to GSI Commerce (founded 1986, acquired by eBay for $2.4B in 2011), spun back out as Radial in 2015 under Sterling Partners and Innotrac, then acquired by bpost in 2017 for $820M, making the underlying technology stack ~30 years old in its oldest layers.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Radial MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Radial doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.