기술 자료

​
​

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
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.

  • 보고 있는 페이지
    • Unity Authentication IDs within payloads


이 페이지의 문제 보고