Amazon Scraper API vs Proxy: Choose a Product Data Source
Compare seller APIs, licensed Amazon product data and proxy page checks by record, access scope and reuse rights.
Read guideMoreLogin's Self-owned Proxy Settings guide documents adding a provider-supplied protocol, host, port, username, and password to a browser profile.
Run proxy detection and a permitted task in that same profile. Hand off its market, session policy, checkpoint, and recovery owner through authorized workspace permissions. Keep credentials out of notes.
The Help Center menu labels were reviewed September 25, 2026. Confirm them in the installed app before adopting this procedure.
Before starting
- A MoreLogin workspace and browser profile that the account owner has authorized the operator to use.
- A ProxyLane endpoint with its protocol, host, port, username, and password available through the team's approved secret handling.
- A permitted test target and a concrete result to check, such as a page field or final URL.
- A required market or location and an agreed recovery contact for the profile.
This walkthrough follows MoreLogin's Self-owned Proxy Settings and Add Proxy help pages, both dated January 22, 2026. Labels depend on the app version.
Warning: Proxy and website credentials can grant route or account access in a shared workspace. Use an approved team profile and workspace permissions. Remove access when the handoff ends. Keep passwords and cookies out of notes and screenshots.
Add the endpoint to a browser profile
MoreLogin's Self-owned Proxy Settings page documents this path for an existing profile: Profiles > Browser, select the profile, then choose Edit Proxy.
For a new profile, use New Profile > Browser Profile > Advanced Settings, then the proxy section. Labels may vary by app version.
In the proxy editor, choose New Proxy or the option to add a custom proxy. Enter the values from your endpoint record, not the example values pictured above:
| Endpoint value | MoreLogin field | Check |
|---|---|---|
| Protocol | Proxy Type |
Choose only the protocol supplied for the endpoint: HTTP, HTTPS, or SOCKS5 |
| Hostname or IP | Proxy host or Proxy server |
Preserve the exact host value |
| Port | Port |
Keep it paired with the supplied host |
| Username | Account or Proxy account |
Use the proxy credential, not the website account name |
| Password | Password |
Paste only into the credential field |
MoreLogin's help page also lists an IP Query Channel, including IP2location, MaxMind, DB-IP, and IP-API. Results can differ by channel.
Record the selected channel when comparing displayed locations. A lookup result does not promise that a target site will use the same market.
Detect the route in the same profile
Save the proxy, run MoreLogin's proxy detection, and start the browser profile. Record the observed exit, selected query channel, profile label, and time in a redacted run record.
Open the permitted target in that same profile and verify the required page or field. Detection checks the route at that moment; it cannot establish target acceptance or the correct market.
Keep the browser-profile test distinct from a cloud phone test. MoreLogin's Self-owned Proxy Settings page documents a separate Profiles > Cloud Phone Profiles path and a separate New Profile > Cloud Phone Profile creation path.
Detection in one environment does not verify the route in the other.
If the detected address or market differs from the expected value, compare the endpoint details and query channel first. Then inspect the target's final URL, content, account state, and access policy.
Record the initial result before refreshing or changing routes, so the cause remains easier to isolate.
Choose a session for the profile's work
Use a separate session name for each independent client profile or task that should keep continuity. ProxyLane's session guide documents a sticky-session name of up to 64 letters and numbers.
The published offer summary states a maximum of up to 7 days while the residential device stays online. Availability changes can end sessions sooner. Separate names do not guarantee separate or exclusive IPs.
MoreLogin's proxy setup help documents Refresh URL for mobile dynamic proxies. It says refreshing a shared mobile proxy can change the access address for every profile using it.
Leave that field empty for residential endpoints unless the provider supplies a compatible refresh URL. Before changing a shared route, notify other profile owners and finish or pause dependent work.
Hand off the profile to a junior operator
Before sending this handoff card, the senior operator should confirm workspace permissions and the intended profile. Include enough context to repeat the task while keeping credentials private:
| Handoff item | Example of the required information |
|---|---|
| Profile | Approved team/profile label and owner |
| Work | Client task, permitted target, required market, and acceptance field |
| Route | Protocol, session name, and when to recheck the exit; never the password |
| Checkpoint | Last verified action, next safe step, and expected result |
| Recovery | Who owns reauthentication, how to confirm the exit, and which actions must not be repeated |
The junior should open the assigned profile, confirm the task and market, recheck its exit, and compare the target result with the acceptance field.
If logged out or the exit changed, stop. Ask the profile owner whether to reauthenticate or start a new permitted session. Reconcile payments, submissions, or other side effects before retrying.
MoreLogin's Profile Settings help page describes groups, tags, and notes for organizing profiles. Use the workspace permissions approved for the client and profile.
Notes can identify owners or tasks. Never store passwords, session credentials, or exported cookies in them.
Troubleshoot by phase
| Observation | Check first | Recovery |
|---|---|---|
| MoreLogin rejects a field | Protocol, host, and port against the endpoint record | Correct the field mapping; do not guess an alternate protocol |
| Proxy detection fails | Endpoint reachability, credentials, and selected query channel | Verify the endpoint through an approved independent check, then rerun detection |
| Detection passes but the target fails | Target status, final URL, account state, market, and policy | Keep this as a target/workflow issue until evidence isolates the route |
| Displayed location is unexpected | Query channel and requested market | Compare a documented query channel and record which one produced the value |
| Several profiles change exit together | Whether they share a mobile proxy and Refresh URL | Pause dependent tasks, tell profile owners, then detect again in each profile |
| Junior cannot resume the task | Profile permission, login state, last checkpoint, and side effects | Stop before repeating an action; ask the named recovery owner |
For an HTTP 407 Proxy Authentication Required, check proxy authentication and entitlement before changing the target or session. A 200 from an IP-check page does not prove task completion.
Keep the profile label, market, protocol, phase, timestamp, redacted exit, and target outcome. Omit credentials and cookies.
Close out the run
Stop the browser profile when the authorized task is complete. Save the redacted result beside the handoff card and record any session interruption, exit change, or recovery step.
For the broader session decision, use the rotating and sticky session guide. For proxy authentication failures, see the 407 troubleshooting guide.
Sources and further reading
ProxyLaneTraffic never expiresPremium residential proxies
From $2/GB
Scale your workflows with the tools you already use. Rotating or sticky sessions up to 72 hours.
