Whiplash Orders API
Order processing — full CRUD, bulk creation, actions, customs info, history, documents, items, serial numbers, shipping details, and wholesale
Whiplash Orders API is one of 10 APIs that Whiplash publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.
This API exposes 18 operations across 16 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 2.0.
Requests are made against a single base URL, https://api.getwhiplash.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Whiplash Orders API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (OAuth2) (bearerAuth).
By default, every request must be authenticated.
bearerAuth— OAuth 2.0 Bearer token. Obtain via authorization code or client credentials flow. See https://help.whiplash.com/hc/en-us/articles/360050870691-Authentication-f…
Paths & Operations 18
Across 16 paths, the API surfaces 18 operations — 14 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Order processing — full CRUD, bulk creation, actions, customs info, history, documents, items, serial numbers, shipping details, and wholesale
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Order (12 properties), Address (11 properties), OrderInput (7 properties), CustomField (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Whiplash 9
Other APIs Whiplash publishes across the network.