Snap Authentication

generated: '2026-07-21'
method: searched
source: https://developers.snap.com/api/marketing-api/Ads-API/authentication
api: Snapchat Marketing API
summary: >-
  The Snapchat Marketing API uses OAuth 2.0 (authorization code grant with
  refresh tokens). Access tokens are Bearer tokens presented in the
  Authorization header and reflect the authorizing user's permissions. Access
  tokens are short-lived (3600 seconds); refresh tokens are long-lived and used
  to mint new access tokens on 401 "token expired".
security_schemes:
  - name: oauth2
    type: oauth2
    flow: authorizationCode
    authorization_endpoint: https://accounts.snapchat.com/login/oauth2/authorize
    token_endpoint: https://accounts.snapchat.com/login/oauth2/access_token
    refresh: true
    token_type: Bearer
    access_token_ttl_seconds: 3600
    header: "Authorization: Bearer {access_token}"
    grants:
      - authorization_code
      - refresh_token
    parameters:
      authorize: [client_id, redirect_uri, response_type=code, scope, state]
      token: [client_id, client_secret, code, grant_type, redirect_uri]
    scopes:
      - snapchat-marketing-api
      - snapchat-offline-conversions-api
      - snapchat-profile-api
snap_kit_login:
  summary: >-
    Snap Kit / Login Kit provides "Login with Snapchat" built on OAuth 2.0 with
    OpenID Connect support for identity, returning approved profile fields.
  docs: https://developers.snap.com/snap-kit/login-kit/Technical-Documentation/OAuth2
  type: [oauth2, openIdConnect]
notes: >-
  Error on expired token returns HTTP 401 with header
  `WWW-Authenticate: Bearer error="invalid_token", error_description="The access
  token expired"`. Many standard OAuth 2.0 client libraries handle the
  refresh-and-retry pattern automatically.