Documentation

​
​

Development

User Acquisition

Monetization

Industry

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 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 error codes

Reference error codes returned by the Vivox SDK for access token operations.
Read time 1 minute
Last updated 8 months ago

The following table details the access token-specific error codes that the Vivox SDK can return from responses to calls that require access tokens.

Error code

Description

20120
Access token already used
20121
Access token expired
20122
Access token has invalid signature
20123
Access token payload claims do not match request parameters
20124
Access token malformed
20125
Unknown error using access tokens
20126
Access token mode not enabled
20127
Access token service unavailable
20128
Access token issuer does not match claims

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