Logiless · OAuth Scopes

Logiless OAuth Scopes

OAuth 2.0 derived

Logiless uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://app2.logiless.com/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

LogisticsE-commerceOrder ManagementWarehouse ManagementInventoryFulfillmentShippingOMSWMSJapan
Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://app2.logiless.com/oauth/v2/auth
Token URL
https://app2.logiless.com/oauth2/token
Flows
authorizationCode

Scopes (0)

Logiless implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-20'
method: derived
source: openapi/logiless-openapi.yml
schemes:
- name: oauth2
  source: openapi/logiless-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://app2.logiless.com/oauth/v2/auth
    tokenUrl: https://app2.logiless.com/oauth2/token
  description: OAuth 2.0 authorization-code flow. Applications must be registered and reviewed
    (3–5 business days) in the LOGILESS Developers console. Access and refresh tokens are valid
    for 30 days. Tokens are issued per LOGILESS user and scoped to that user's merchant data.
scopes: []