Zaptec Authentication

generated: '2026-10-28'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.zaptec.com/docs/api-authentication.md
sources:
- https://docs.zaptec.com/docs/api-authentication.md
- https://docs.zaptec.com/docs/webhook-authentication.md
- https://docs.zaptec.com/reference/post_chargers-chargerid-onboarding.md
- https://docs.zaptec.com/reference/post_chargers-chargerid-onboarding
description: Zaptec uses OAuth 2.0 Resource Owner Password Credentials (ROPC) grant to obtain a bearer token that is sent in the Authorization
  header. Webhook authentication can also use HTTP Basic when no authentication URL is provided.
schemes:
- type: http-bearer
  name: OAuth2 ROPC Bearer Token
  evidence: Authenticate with the ZapCloud API and Zaptec integrations API  by requesting an OAuth bearer token and sending it in the Authorization
    header for protected API requests.
  location: header
  header: Authorization
  flows:
  - password
  token_url: https://api.zaptec.com/oauth/token
  scopes:
  - openid
  how_to_obtain: Obtain a user group with owner or service permissions, then POST to https://api.zaptec.com/oauth/token with grant_type=password,
    username, password, and optional scope=openid.
- type: http-basic
  name: Webhook Basic Authentication
  evidence: If an Authentication URL is *not* provided, the username and password from the payload are included in the Authorization header using
    HTTP Basic authentication.
  location: header
  header: Authorization
  how_to_obtain: Provide username and password in the webhook payload; Zaptec will include them in the Authorization header using HTTP Basic.
docs: https://docs.zaptec.com/docs/api-authentication.md