Lightspeed Retail (X-Series) API Connection
Generate a Personal Token for Lightspeed Retail (X-Series) and prepare the Store URL and Personal Token required by Next-Cart.
Lightspeed Retail (X-Series) API Connection
Section titled “Lightspeed Retail (X-Series) API Connection”Lightspeed Retail (X-Series) uses a Personal Token for the Next-Cart API connection when that credential option is available in the Retail POS account. If the edition is not yet confirmed, use the Lightspeed Overview to compare all supported Lightspeed editions before continuing.
Get the connection details
Section titled “Get the connection details”-
Sign in to the Retail POS admin for the store used in the migration and open Setup > Personal tokens.
-
Click Add Personal token.
-
Enter Token name. Leave Expiry date disabled when the token must remain available for the migration workflow.
-
Click Generate personal token.
-
Copy the displayed Personal Token before closing the dialog. The token text cannot be viewed again after the dialog is closed.
Enter the values in Next-Cart
Section titled “Enter the values in Next-Cart”| Next-Cart field | Value to enter |
|---|---|
| Store URL | The Lightspeed Retail (X-Series) store URL. |
| Personal Token | The Personal Token generated for the intended Retail POS store. |
Verify this connection
Section titled “Verify this connection”Use Test Platform Connections for optional access verification. A successful test shows Connected.
| Check | Pass condition |
|---|---|
| Store identity | The Store URL identifies the intended Lightspeed Retail (X-Series) store or site, and the connection values used below belong to that same environment. |
| Credential or value | Personal Token is the value obtained for this same intended Lightspeed Retail (X-Series) store, account, or authorization setup. |
| Token type | The value is a valid Personal Token, not a private-app application token. |
A Connected result confirms that Next-Cart can access Lightspeed Retail (X-Series) with the supplied connection values. It does not confirm migration configuration, mappings, or final migrated data; validate those separately during the Configuration step and post-migration review.
If the platform remains Not connected, confirm the Store URL and active Personal Token belong to the intended store. Do not substitute a private-app token into the Personal Token field; then use the shared recovery checks.