Miva Merchant API Connection
Prepare Miva Merchant API connection values for a Next-Cart migration service when API setup is shown for Miva Merchant.
Miva Merchant API Connection
Section titled “Miva Merchant API Connection”A valid Miva Merchant API connection gives Next-Cart the authorized platform access required by the selected migration path.
Next-Cart may ask for your Miva Merchant store URL, Endpoint URL, and Access Token. Prepare these values from the correct Miva admin account before you test the connection.
When to use this guide
Section titled “When to use this guide”Use this guide when:
- Miva Merchant is the Source Platform or Target Platform in your selected migration path;
- Next-Cart shows Miva Merchant API setup;
- Next-Cart asks for Store URL, Endpoint URL, Access Token, or related Miva connection values.
Prerequisites
Section titled “Prerequisites”Before you begin, confirm that:
| Requirement | Why it matters |
|---|---|
| Miva admin access | You need access to create or view API tokens. |
| Permission to manage API tokens | Your user role must allow token creation and group assignment. |
| Access to the correct store | The token must belong to the store selected in your migration path. |
| Secure storage | API credentials should be copied only into approved secure locations. |
Required values
Section titled “Required values”| Required value | Where to prepare it | Notes |
|---|---|---|
| Store URL | Miva public store URL | Use the store URL requested by the Next-Cart interface. |
| Endpoint URL | API Token details | Copy the endpoint shown for the token. |
| Access Token | API Token details | Copy the token exactly as shown. |
Prepare the API connection values
Section titled “Prepare the API connection values”- Sign in to Miva Admin.
- Open Settings, then User Management, then API Tokens.
- Click Add API Token.
- Enter a clear name for the token, such as Next-Cart Migration Service.
- Review the generated Endpoint URL and Access Token.
- Configure Allowed IPs and other security options according to your store policy.
- Save the token.
- Return to the API Tokens list and open the token groups.
- Assign groups that allow access to the data included in your migration scope, such as product management, customer service, order fulfillment, marketing, and reporting groups where required.
- Copy the Store URL, Endpoint URL, and Access Token into a secure temporary location.
Enter the values in Next-Cart
Section titled “Enter the values in Next-Cart”In the Next-Cart connection setup screen, enter only the values requested by the interface.
| Next-Cart field | Platform value |
|---|---|
| Store URL | Miva public store URL requested by Next-Cart. |
| Endpoint URL | Endpoint URL from the API Token details. |
| Access Token | Access Token from the same token details. |
Expected result
Section titled “Expected result”The Miva Merchant API connection values are ready to test in Next-Cart.
Verify the connection
Section titled “Verify the connection”| Check | Pass condition |
|---|---|
| Store match | The Store URL belongs to the Miva store in the selected migration path. |
| Endpoint completeness | The full Endpoint URL is copied exactly as shown. |
| Token access | The token has groups that cover the selected migration data types. |
| Connection test | Next-Cart can authenticate and read supported Miva data. |
If the connection fails
Section titled “If the connection fails”| Issue | What to check |
|---|---|
| Authentication error | Copy the Access Token again and check for extra spaces or missing characters. |
| Endpoint error | Confirm that the Endpoint URL is copied from the same API token. |
| Permission error | Review token groups and assign the required access for selected data types. |
| Access restriction | Check Allowed IPs or other security controls that may block connection testing. |
Security cleanup
Section titled “Security cleanup”After migration work is complete and verified:
- remove or revoke temporary API credentials where the platform provides that option;
- reduce access if a broader permission set was used only for migration work;
- remove copied credentials from insecure notes, tickets, chats, or shared files;
- review the store admin account or API user used for API setup.
Next step
Section titled “Next step”| Goal | Go to |
|---|---|
| Test the connection | Verify Platform Connections |
| Fix an authentication or permission issue | Troubleshoot Connection Setup |
| Continue after the connection passes | Configure Your Migration |