Skip to content
Back to Site

ShopBase API Connection

Create a ShopBase private app and enter the Store URL, API Key, and Password required by Next-Cart.

Create a private app to obtain the API Key and Password required by the ShopBase connection.

  1. Sign in to ShopBase and open Apps.

  2. Click Manage private apps near the bottom, then Create a new private app.

    ShopBase – Manage private apps

  3. Enter the private app name and your email address in Emergency developer email.

  4. In Admin API, click Review disabled Admin API permissions. Set the following resources to Read or Read and write as provided by the permission control:

    • Store content such as pages and redirects.
    • Customer details and customer groups.
    • Orders, transactions, and fulfillments.
    • Products, variants, and collections.
    • Theme templates and assets.
    • Discounts.
    • Inventory.

    ShopBase API permissions

  5. Click Save and confirm creation of the private app.

  6. In the Admin API section, copy API Key and Password.

  7. Prepare the original store address in the form https://xxxxxx.onshopbase.com.

Next-Cart fieldValue to enter
Store URLThe original address in the form https://xxxxxx.onshopbase.com.
API KeyThe API Key shown for the private app.
PasswordThe app’s Password (API Password), not the administrator account password.

Use Test Platform Connections for optional access verification. A successful test shows Connected.

CheckPass condition
Store identityThe Store URL identifies the intended ShopBase store or site, and the connection values used below belong to that same environment.
Credentials and valuesAPI Key, Password are the values obtained for this same intended ShopBase store, account, or authorization setup.
Permissions or accessThe private app retains the required Admin API permissions for the migration scope.

A Connected result confirms that Next-Cart can access ShopBase 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 API Key and Password come from the same private app and that its Admin API permissions still cover the migration scope, then use the shared recovery checks.