Documentation

​
​

Development

User Acquisition

Monetization

Industry

Vivox Unity SDK

Vivox Unity SDK

Vivox
​
​
Vivox Unity SDK
  • Overview
  • Get started
  • Release notes
  • Developer guide
  • Tutorials
    • Implement Vivox Unity
    • Access Token Developer Guide
      • Access token terminology
      • Requests that require access tokens
      • Access token identifiers
      • Access token format
        • Access token header
        • Access token payload
        • Access token signature
        • Supported values for the Vivox action claim
      • Access token examples
      • Generate a token from the client
      • Generate a token on a secure server
      • Key update API
      • Access token error codes
  • Reference
  1. Vivox Unity SDK documentation

Access token signature

Learn how Vivox access tokens are signed using HMAC SHA256.
Read time 1 minute
Last updated 8 months ago
The signature is the base64url-encoded HMAC of the first two parts:
base64UrlEncode(HMACSHA256(base64UrlEncode(header) + '.' + base64UrlEncode(payload), key))
The encoded header and encoded payload are joined with a period, undergoes HMAC with the token signing key, and then the entirety is encoded.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

    Report a problem with this page