文档

​
​

Development

User Acquisition

Monetization

工业

Vivox Core SDK

Vivox Core SDK

此页面不支持所选语言。
Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
  • Reference
    • 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
      • Override development key generation
      • Access token error codes
    • Server to Server Web API Reference Guide
    • Core API Reference Manual
    • Third-party license information
  • Privacy overview
  1. Vivox Core SDK documentation

Access token payload

Understand the payload section of a Vivox Access Token.
阅读时间3 分钟
最后更新于 6 个月前

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, see 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
注意
It is the
f
and
sub
fields that will need this format to work with UAS.
注意
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.
注意
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
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。

  • 在本页上
    • Unity Authentication IDs within payloads


报告此页面的问题