Vend API Connection

Vend API Connection

Vend uses a Personal Token for the Next-Cart API connection when that credential option is available in the Retail POS account.

Get the connection details

Personal Token availability

Lightspeed is replacing legacy Personal Tokens with private apps. Newer Retail POS accounts, and accounts that have moved to private apps, may no longer show Setup > Personal tokens. Next-Cart requests a Personal Token for this connection profile. If Personal tokens is unavailable, do not substitute a private-app application token into the Personal Token field; use Support Tickets to confirm the supported connection path.

1. Sign in to the Retail POS admin for the store used in the migration and open Setup > Personal tokens.

2. Click Add Personal token.

3. Enter Token name. Leave Expiry date disabled when the token must remain available for the migration workflow.

4. Click Generate personal token.

5. 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

Next-Cart field	Value to enter
Store URL	The Vend store URL.
Personal Token	The Personal Token generated for the intended Retail POS store.

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 Vend 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 Vend 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 Vend 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 application token into the Personal Token field; then use the shared recovery checks.