Set Up an API Connection

Set Up an API Connection

Use this page when Connect Stores assigns API setup to the selected platform. Follow the matching platform-specific guide for authorization, permissions, credential preparation, and the exact values requested by Next-Cart.

Use only the fields assigned to the selected platform

API requirements differ by platform. A Store URL is not universal: if Connect Stores does not provide that field for the selected Source or Target setup, do not add or substitute one.

Open the correct API guide

API Connection Guides Find the platform guide for credential preparation, authorization, required permissions, and Next-Cart connection fields.

Connection Setup Requirements Resolve method, edition, or platform-name choices before preparing API credentials.

If the API directory does not contain a dedicated guide for the selected platform, use only the fields and instructions provided for that selection in Connect Stores. Do not infer missing values from another platform. Contact Support if the requested credential type is unclear.

After the platform credentials are ready

Switch back to the Next-Cart migration setup interface, where Connect Stores is already open, and enter the prepared values into the matching platform fields. Keep each URL, token, key, ID, secret, username, or password with the same store and authorization context that produced it.

If the selected setup includes a Store URL, confirm that it identifies the intended store before continuing. If no Store URL field is present, do not invent one. For paid migrations, Store URL Locking and Store Identity explains which available Source or Target URL can lock after Connect Stores is saved and the migration advances to Configuration. Test Connection alone does not create the lock.

Test Connection is optional, not a prerequisite for proceeding. If access fails, Next-Cart displays a pop-up notification and Not connected beside the affected platform. Use Test Platform Connections for optional checks and failure handling. Platform-specific credential problems remain in the corresponding API guide; shared connection-test failures belong to Troubleshoot Connection Setup.

Protect connection credentials

Use only the permissions required by the platform guide and migration scope. Keep tokens, secrets, passwords, and private keys in approved secure storage. After migration work is complete and accepted, revoke temporary credentials or apps when the platform guide instructs you to do so.

Do not place full tokens, client secrets, private keys, passwords, or Backup Codes in unprotected support messages.