How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Whiplash Customers API

Customer management — list, count, retrieve, update, and available actions

Whiplash Customers API is one of 10 APIs that Whiplash publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.

This API exposes 5 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.getwhiplash.com.

5 operations 4 paths 4 schemas 4 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.getwhiplash.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Whiplash Customers 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 5

Across 4 paths, the API surfaces 5 operations — 4 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Customers 5

Customer management — list, count, retrieve, update, and available actions

GET
/v2/customers
List customers
listCustomers 2 params → 200401
GET
/v2/customers/count
Count customers
countCustomers → 200401
GET
/v2/customers/actions
List available customer actions
listCustomerActions → 200401
GET
/v2/customers/{id}
Retrieve a customer
getCustomer 1 param → 200401404
PUT
/v2/customers/{id}
Update a customer
updateCustomer 1 param body → 200401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Customer (15 properties), Address (11 properties), CustomField (2 properties), CountResponse (1 property). Each schema is shown below with its type and property counts.

Address
object
11 properties
CustomField
object
2 properties 2 required
Customer
object
15 properties 4 required
CountResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

whiplash-customers-api-openapi.yml Raw ↑

Other APIs Whiplash publishes across the network.

Whiplash Bundle Items API
Whiplash Consumer Returns API
Whiplash Documents API
Whiplash Items API
Whiplash Notification Events API
Whiplash Notification Subscriptions API
Whiplash Orders API
Whiplash Shipnotices API
Whiplash Simulate API
Where this information came from

This is an independent, third-party profile of Whiplash Customers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.