Set Up an API Connection
Use the platform-specific API guide to prepare the exact credentials and connection values requested for the selected platform in the Connect Stores step.
Set Up an API Connection
Section titled “Set Up an API Connection”When Connect Stores assigns API setup to the selected platform, follow the matching platform-specific connection guide for authorization, permissions, credential preparation, and the exact values requested by Next-Cart.
Open the correct API guide
Section titled “Open the correct API guide”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 the Connect Stores step. Do not infer missing values from another platform. Contact Support if the requested credential type is unclear.
After the platform credentials are ready
Section titled “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 locks when the successfully connected setup proceeds from the Connect Stores step to the Configuration step. Running Test Connection does not create the project lock by itself.
Use Test Platform Connections when you need to verify access or handle Not connected. Platform-specific credential problems remain in the corresponding API guide; shared connection-test failures belong to Troubleshoot Connection Setup.
Protect connection credentials
Section titled “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.