Power2Sme Authentication

generated: '2026-07-20'
method: derived
source: openapi/power2sme-openapi.json (operations + 401/403 responses)
provider: power2sme
api: POWER2SME API
notes: >-
  The Swagger 2.0 document declares no `securityDefinitions`, so no formal
  security scheme could be derived from the spec. Access is gated by a
  login / OTP token model exposed through the operations themselves: callers
  authenticate via the Sign In (customerloginUsingPOST) or OTP flow
  (generateOtp* / validateOtp*) and every operation returns 401 Unauthorized
  and 403 Forbidden, indicating a bearer/session token is expected on
  subsequent calls. Token transport is not documented in the spec.
schemes: []
flows:
- kind: login-token
  evidence:
  - operation: customerloginUsingPOST
    path: /customerlogin
    summary: Sign In
  - operation: createPasswordUsingPOST
    path: /createpassword
    summary: Create New Password
  - operation: changePasswordUsingPOST
    path: /changepassword
    summary: Change Password
- kind: otp
  evidence:
  - operation: generateOtpUsingPOST_3
    path: /generateotp
    summary: Generate OTP
  - operation: validateOtpUsingPOST_3
    path: /validateotp
    summary: Validate OTP
unauthorized_responses:
  '401': present on all 49 operations
  '403': present on all 49 operations