ePages API Connection

ePages API Connection

A valid ePages API connection gives Next-Cart the authorized platform access required by the selected migration path.

Next-Cart may ask for your ePages Source Store URL, API URL, and Access Token. Prepare these values from your ePages store and private app setup before entering them in Next-Cart.

Confirm the exact URL format requested

ePages setups may use both the live store URL and an API URL. Enter each value in the field requested by the Next-Cart interface.

When to use this guide

Use this guide when:

• ePages is the Source Platform or Target Platform in your selected migration path;
• Next-Cart shows ePages API setup;
• you have permission to create or manage private apps in ePages.

Prerequisites

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.

Required values

Required value	Where to prepare it	Notes
Source Store URL	Live ePages store	Copy the public store URL.
API URL	Live store URL with the API path requested by Next-Cart	Common setups append /api to the store URL. Confirm against the Next-Cart field.
Access Token	ePages private app	Copy the token generated for the private app.
Client ID or Client Secret	ePages private app, if shown and requested	Enter only if Next-Cart asks for these values.

Prepare ePages API values

1. Visit your live ePages store and copy the Source Store URL.
2. Prepare the API URL requested by Next-Cart. If the setup uses the standard API path, append /api to the store URL.
3. Sign in to your ePages admin.
4. Open Apps.
5. Create a private app.
6. Give the private app a clear name, such as Next-Cart Migration.
7. Assign read permissions for the data types included in the migration scope, such as products, categories, orders, and customers.
8. Save the app.
9. Copy the Access Token.
10. Copy the Client ID or Client Secret only if they are shown and Next-Cart requests them.

Enter the values in Next-Cart

In the Next-Cart connection setup screen for ePages, enter the values requested by the interface.

Next-Cart field	ePages value
Source Store URL	Live ePages store URL.
API URL	API URL requested by Next-Cart.
Access Token	Private app Access Token.
Client ID or Client Secret	Private app value, if requested.

Expected result

The ePages API values are ready to test in Next-Cart.

Verify the connection

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 fails

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.
Client value missing	Enter Client ID or Client Secret only if Next-Cart requests it.

Security cleanup

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.

Next step

Goal	Go to
Test the connection	Verify Platform Connections
Fix a URL, token, or permission issue	Troubleshoot Connection Setup
Continue after the connection passes	Configure Your Migration