# Proof Key for Code Exchange (PKCE) update

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

The **User Authorization** use case supports [Proof Key for Code Exchange (PKCE)](https://datatracker.ietf.org/doc/html/rfc7636) for private or public apps. Use PKCE when you don't have or don't want to use a backend server for user authorization. Zoom offers a separate public client ID in the authorization request that doesn't require an associated client secret.

PKCE is useful for facilitating the OAuth flow on the client side, like to offer user authorization on mobile devices with Zoom Meeting SDK.

See [using Proof Key for Code Exchange (PKCE)](/docs/integrations/oauth/#using-proof-key-for-code-exchange-pkce) for details.