Comparison Table: V1 vs V2 Authentication
Introduction
This article outlines the differences between V1 and V2 authentication methods for the Lightspeed Restaurant K-Series APIs.
Key Differences Between V1 and V2 Authentication
| Feature | V1 Authentication | V2 Authentication |
|---|---|---|
| Authorization URL - TRIAL | https://api.trial.lsk.lightspeed.app/oauth/authorize | https://auth.lsk-demo.app/realms/k-series/protocol/openid-connect/auth |
| Authorization URL - PRODUCTION | https://api.lsk.lightspeed.app/oauth/authorize | https://auth.lsk-prod.app/realms/k-series/protocol/openid-connect/auth |
| Token URL - TRIAL | https://api.trial.lsk.lightspeed.app/oauth/token | https://auth.lsk-demo.app/realms/k-series/protocol/openid-connect/token |
| Token URL - PRODUCTION | https://api.lsk.lightspeed.app/oauth/token | https://auth.lsk-prod.app/realms/k-series/protocol/openid-connect/token |
| Scopes | See Access Scopes | All previous scopes can be requested. Optional scope offline_access now available. See Offline Access for more information. All clients will automatically request User Profile and Email scopes, in addition to the scopes specified |
| Token Expiry | Tokens expire after 60 minutes | Token expiry variable, must be checked dynamically |
| Refresh Tokens | Expire after 14 days | Refresh token expiry variable, must be checked dynamically. Tokens without offline_access will have a shorter lifespan. |
| Token Request Method | POST with URL parameters | POST with parameters in request body. |