Whiplash Merchandising · Authentication Profile

Whiplash Merchandising Authentication

Authentication

Whiplash Merchandising secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyFulfillmentLogisticsEcommerceShippingWarehousingInventory3PLOrder ManagementReturnsSupply Chain
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

OAuth2 oauth2
· flows: authorizationCode

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://www.getwhiplash.com/.well-known/oauth-authorization-server
docs: https://developers.getwhiplash.com
summary:
  types: [oauth2]
  oauth2_flows: [authorizationCode]
  pkce: S256
  notes: >-
    The published OpenAPI (Rydership V2) does not declare securitySchemes, but
    every operation returns 401 unauthorized / 403 forbidden and the live
    RFC 8414 OAuth Authorization Server Metadata document confirms OAuth 2.0.
    API access is invite-only (request form via help.whiplash.com).
schemes:
- name: OAuth2
  type: oauth2
  source: https://www.getwhiplash.com/.well-known/oauth-authorization-server
  issuer: https://www.getwhiplash.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://www.getwhiplash.com/oauth/authorize
    tokenUrl: https://www.getwhiplash.com/oauth/token
    registrationUrl: https://www.getwhiplash.com/oauth/register
    responseTypes: [code]
    grantTypes: [authorization_code, refresh_token]
    codeChallengeMethods: [S256]
    tokenEndpointAuthMethods: [none, client_secret_post]