Whiplash Merchandising
Whiplash (now Ryder E-commerce by Whiplash) is an order-fulfillment and third-party logistics (3PL) platform for direct-to-consumer and ecommerce brands. It runs a network of fulfillment centers offering pick-pack-ship, warehousing, inventory management, kitting, omnichannel order routing, and returns processing. The company exposes the Rydership V2 REST API (formerly the Whiplash API) so merchants and platforms can programmatically manage items, orders, order items, shipments (ship notices), consumer returns, customers, documents, and webhook notification subscriptions across the fulfillment lifecycle. Whiplash was founded in 2011, backed by 500 Global, and acquired by Ryder System in 2021.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Whiplash Merchandising the way a machine reads it — 25 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Whiplash Merchandising scores 49.4/100 (developing), with a separate agent-readiness read of 61/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Whiplash Merchandising
Each block below is one kind of artifact we hold for Whiplash Merchandising. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Whiplash Merchandising bundle_items API
Bundle Items are components that make up a bundle, defining the quantity and relationship of items within product bundles.
Whiplash Merchandising consumer_returns API
A ConsumerReturn represents goods coming back from an end consumer. It is a special form of Shipnotice, and is processed in much the same way.
Whiplash Merchandising customers API
Customers are Whiplash clients, not the End Consumer. Most Whiplash resources are owned by a Customer (or belong to resources that are).
Whiplash Merchandising documents API
Documents are imported files and exported reports. We store a record in your account of every file you import, as well as every report you've run, so they're easy to search and ...
Whiplash Merchandising items API
Items are probably the most fundamental entity in the Whiplash system. An item is simply a 'shippable unit'. So, it's not a Whiplash T-Shirt; it's a Small Whiplash T-Shirt, for ...
Whiplash Merchandising load_scacs API
The load_scacs API from Whiplash Merchandising — 2 operation(s) for load_scacs.
Whiplash Merchandising notification_events API
System event definitions for notifications.
Whiplash Merchandising notification_subscriptions API
User notification preferences and subscriptions.
Whiplash Merchandising order_documents API
Order-related documentation and paperwork.
Whiplash Merchandising order_items API
An OrderItem represents an Item with a quantity in an Order.
Whiplash Merchandising order_totes API
Order picking container management.
Whiplash Merchandising orders API
Orders are end consumer requests for Items. An Order is comprised of OrderItems. Orders represent outgoing stock.
Whiplash Merchandising originators API
Originators are e-commerce, API, or ERP representations of an Item, Order, OrderItem, ConsumerReturn, Shipnotice, or ShipnoticeItem. They contain your system's ID and, optionall...
Whiplash Merchandising packages API
Shipment package details and tracking.
Whiplash Merchandising projects API
Project management and organization.
Whiplash Merchandising scancodes API
Barcode management and processing.
Whiplash Merchandising shipnotice_items API
Similar to an OrderItem, ShipnoticeItem represents an Item with a quantity in a Shipnotice. quantity refers to the quantity expected to arrive, and the quantity actually receive...
Whiplash Merchandising shipnotices API
A Shipnotice is the opposite of an order, and are notifications by the client of inventory that is expected to arrive at a warehouse. Shipnotices represent incoming stock.
Whiplash Merchandising simulate API
(Sandbox Only) Simulate Order and Ship Notice processing, since these are staff-only operations.
Whiplash Merchandising templates API
Templates allow you to customize packing slips, email confirmations, order inserts, etc.
Whiplash Merchandising wholesale_items API
The wholesale_items API from Whiplash Merchandising — 2 operation(s) for wholesale_items.
Scroll within the panel for all 21 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
whiplash-merchandising-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Whiplash Merchandising — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/whiplash-merchandising · machine-readable index on apis.io