What you are building Use Watch for
A headless storefront that runs in the browser (PWA Kit or your own SPA) A public SLAS client, with the authorization code flow and PKCE Refresh tokens are single use. Each refresh returns a new one, and the app has to store it, or the shopper's next refresh fails.
A storefront with a server in front of it (backend-for-frontend, full-stack app) A private SLAS client, with the secret kept on the server The secret must never reach the browser bundle. If it does, treat it as leaked and rotate it.
An ERP, OMS, PIM or warehouse integration with no shopper involved An Account Manager API client calling the Admin APIs Scopes. A token without the sfcc scope for the resource you call (orders, products, inventory) is rejected even when the client itself is valid.
Logic the standard endpoints don't cover A custom API in a cartridge, or a hook on an existing endpoint Custom APIs need an OAS 3.0 contract, an api.json mapping and a script whose function name matches the operationId. A mismatch fails quietly at registration.