Documentation

​
​

Development

User Acquisition

Monetization

Industry

Vivox Unreal SDK

Vivox Unreal SDK

Vivox
​
​
Vivox Unreal SDK
  • Overview
  • Get started
  • Release notes
  • Developer guide
  • Tutorials
  • Reference
    • Vivox Core Unreal class model overview
    • Vivox Unreal conventions
    • Unreal API Reference Manual
    • 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 on the client
      • Generate a token on a secure server
      • Key update API
      • Access token error codes
    • Server to Server Web API Reference Guide
    • Third-party license information
  1. Vivox Unreal SDK documentation

Access Token Payload

Understand the payload section of a Vivox Access Token.
Read time 3 minutes
Last updated 8 months ago

The payload is a base64url-encoded JSON object that contains the claims asserted by the token. You can list claims in the payload in any order.
The following table details the claims that you can use in a token. For more information on which parameters are required for each token, refer to Access token examples.

Unity Authentication IDs within payloads

If your application is using Unity Authentication Service to authenticate players, you can use the UAS ID within a Vivox access token to ensure proper player identity. SIP URIs, which are used to identify players, must be in the proper format to ensure that the player ID is parsed from the full SIP URI. This format is mandatory for using any Unity Moderation service with VATs.
The following is an example of the expected SIP format:
sip:.issuer.unity_player_id.unity_environment_id.@domain.vivox.com
Note
It is the
f
and
sub
fields that will need this format to work with UAS.
Note
Ensure that you only include the parameters from the example. Claims that contain the wrong parameters return
invalid signature
or
malformed payload
errors on the API calls.
ClaimExample valueDescription
vxi
1
Guarantee token uniqueness. If all other claims are identical, this must be different or the token could be rejected as already used. Note: It's recommended that you use an unsigned integer that is increased by 1 for every token that is generated.
sub
sip:[.blindmelon-AppName-dev.jerky.@tla.vivox.com](mailto:.blindmelon-AppName-dev.jerky.@tla.vivox.com)
The subject. A user SIP URI that is used for mute and kick actions. This is the user who is muted or unmuted, or the user who is kicked.
f
sip:[.blindmelon-AppName-dev.beef.@tla.vivox.com](mailto:.blindmelon-AppName-dev.beef.@tla.vivox.com)
From. This is a user SIP URI that is used in all actions. This is the user who performs actions such as signing in, joining the channel, or muting another user.
iss
blindmelon-AppName-dev
An application-specific issuer. The issuer is provided when you create an application on the Unity Dashboard.
vxa
kick
A Vivox action. For more information, see Supported values for the Vivox action claim.
t
sip:[confctl-g-blindmelon-AppName-dev.testchannel@tla.vivox.com](mailto:confctl-g-blindmelon-AppName-dev.testchannel@tla.vivox.com)
To. This is a channel SIP URI that is used in join, mute, kick, and transcription actions. This is the channel where the action takes place.
exp
1600349400
The expiration time as epoch seconds. This value is usually the current time plus 90 seconds.

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.

  • On this page
    • Unity Authentication IDs within payloads


Report a problem with this page