Swipeguide · Authentication Profile

Swipeguide Authentication

Authentication

Swipeguide secures its APIs with apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyManufacturingWork InstructionsFrontlineShop FloorMaintenanceConnected WorkerSmart ManufacturingIndustrial
Methods: apiKey Schemes: 3 OAuth flows: API key in: query, header, body

Security Schemes

apiKeyQuery apiKey
· in: query (auth)
apiKeyHeader apiKey
· in: header (L2LAUTH)
apiKeyBody apiKey
· in: body (auth)

Source

Authentication Profile

swipeguide-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://support.leading2lean.com/hc/en-us/articles/360051148492-API-Documentation
docs: https://support.leading2lean.com/hc/en-us/articles/360051148492-API-Documentation
summary:
  types: [apiKey]
  api_key_in: [query, header, body]
  request_signing: hmac-sha512
  oauth2_flows: []
notes: >-
  The L2L Dispatch API authenticates every HTTPS request with an API Key. API
  Keys are created exclusively by L2L Support for an API user account (contact
  support@leading2lean.com). For sensitive operations a separate Secret Key can
  sign requests using HMAC-SHA512 to guarantee they were not tampered with.
schemes:
- name: apiKeyQuery
  type: apiKey
  in: query
  parameter: auth
  description: API key supplied as the `auth` query parameter.
- name: apiKeyHeader
  type: apiKey
  in: header
  parameter: L2LAUTH
  description: API key supplied in the `L2LAUTH` HTTP header.
- name: apiKeyBody
  type: apiKey
  in: body
  parameter: auth
  description: API key supplied as `auth` in the POST request body.
request_signing:
  algorithm: HMAC-SHA512
  key: secret-key
  scope: sensitive operations
  description: >-
    Optional request signing using a Secret Key (distinct from the API Key) to
    verify request integrity for sensitive operations.