ePages API Connection
Create the ePages private-app access token and enter the Store URL, API URL, and Access Token required by Next-Cart.
ePages API Connection
Section titled “ePages API Connection”A valid ePages API connection gives Next-Cart the authorized platform access required by the selected migration path.
Get the connection details
Section titled “Get the connection details”Before you begin
Section titled “Before you begin”Before you begin, confirm that:
| Requirement | Why it matters |
|---|---|
| ePages admin access | You need access to create or manage apps. |
| Live store URL | The API URL is often derived from the live store URL. |
| Permission to create private apps | Next-Cart may require a private app access token. |
| Data scope is known | App permissions should cover the data types included in the migration scope. |
| Secure credential handling | App tokens and secrets should be stored safely. |
- Visit your live ePages store and copy the Source Store URL.
- Prepare the API URL requested by Next-Cart. If the setup uses the standard API path, append
/apito the store URL. - Sign in to your ePages admin.
- Open Apps.
- Create a private app.
- Give the private app a clear name, such as Next-Cart Migration.
- Assign read permissions for the data types included in the migration scope, such as products, categories, orders, and customers.
- Save the app.
- Copy the Access Token.
Enter the values in Next-Cart
Section titled “Enter the values in Next-Cart”| Next-Cart field | Value to enter |
|---|---|
| Store URL | Live ePages store URL. |
| API URL | API URL used by the ePages connection. |
| Access Token | Private app Access Token. |
Verify the connection
Section titled “Verify the connection”Test Connection is optional. A failed connection displays a pop-up notification and Not connected beside the affected platform; correct that issue before continuing.
| Check | Pass condition |
|---|---|
| URL format | Store URL and API URL are entered in the correct fields. |
| Authentication | The Access Token is accepted. |
| Permissions | The private app can read the data types included in the migration scope. |
| Store match | The app belongs to the intended ePages store. |
If the connection does not pass
Section titled “If the connection does not pass”| Issue | What to check |
|---|---|
| API URL error | Confirm whether Next-Cart expects the public store URL, the API URL, or both. |
| Access token rejected | Re-copy the token from the private app or create a fresh private app. |
| Missing data access | Review app permissions and confirm that the required data types are included. |
| Wrong store | Confirm the private app was created in the ePages store used for the migration path. |
After migration
Section titled “After migration”After migration work is complete and verified:
- remove the private app if it is no longer needed;
- revoke or rotate exposed tokens;
- remove copied credentials from insecure notes or shared files.