Amazon Scraper API vs Proxy: Choose a Product Data Source
Distinguish authorized Amazon APIs, licensed product data and proxy-based page checks by record quality and access rights.
Read guideAdsPower binds proxy settings to a browser profile. To use a ProxyLane endpoint, create or edit the profile, select the endpoint's protocol, run Check Proxy, and open the profile's detection page. That confirms the browser can connect to the proxy. A separate check against the permitted target confirms whether the work itself succeeded.
Create a profile with a custom proxy
AdsPower's documented quick path is New profile, choose Custom in the proxy area, enter the proxy details, click Check proxy, and click OK. The supported paste format is IP:port:username:password; AdsPower says the other fields are filled automatically from that value. The same proxy area also offers No Proxy (Local network) when a profile should use a direct connection.
If your endpoint record is already split into fields, use the explicit controls instead. AdsPower documents HTTP, HTTPS, and SOCKS 5 with Host:Port, Proxy username, and Proxy Password. It also documents SSH and a no-proxy option, but select only the protocol your endpoint actually provides.
| Endpoint value | AdsPower field | Acceptance check |
|---|---|---|
| Protocol | Proxy type | HTTP, HTTPS, or Socks5 must match the provider record |
| Host and port | Host:Port | Use the supplied host and numeric port together |
| Username | Proxy username | Keep it in the protected field or saved proxy record |
| Password | Proxy Password | Never place it in a profile note, screenshot, or page script |
| Mobile IP control URL | Change IP URL | Use only when the provider documents it for a mobile proxy |
AdsPower also supports Saved Proxies. A saved record can be selected instead of retyping the endpoint, and the profile page can assign a saved proxy at creation time. Check that the selected saved record is the one intended for this profile; a profile name alone does not tell you which live route it uses.
Check the browser route
Click Check Proxy before opening the profile. AdsPower describes a passed connection test as a successful connection to the proxy and a failed test as an inability to connect. Keep the protocol, host label, profile identifier, result, and timestamp in a redacted run record.
Open the profile from the Profiles page after it passes. AdsPower says the browser opens with a default start page that acts as a proxy detection page and shows the current IP and other browser information. Compare that observation with the route you intended to use, then open the permitted target in the same profile and validate a concrete result such as the final URL, page title, or required field.
The route check does not establish target authorization or content. If the target returns a sign-in page, challenge, 403, 429, or an empty application shell, classify that separately from proxy connectivity. The proxy error 407 guide covers authentication failures, while the curl proxy guide is useful for a separate transport probe before the browser test. The antidetect browser proxy setup guide covers the shared profile concepts.
Handle mobile Change IP URL carefully
AdsPower documents Change IP URL as an option for mobile proxies. Refreshing it can change the proxy IP, and AdsPower says that when multiple profiles use the same proxy, the change can affect each profile. Treat this as a shared route change. Pause related work, refresh deliberately, reopen or recheck the affected profiles, and record the new observation.
Do not fill Change IP URL with a guessed endpoint. Leave it empty when the provider has not supplied a mobile control URL. A rotating route can be correct for independent requests and wrong for a sequence that relies on one session. For the protocol trade-off, see HTTP versus SOCKS5 proxies.
Configure global safeguards with care
AdsPower's global browser settings include an option to open a profile only when its proxy is available. That can prevent a profile from opening when the endpoint is down, but it does not validate the target's response. AdsPower also documents matching timezone and location when a dynamic IP changes. Treat that setting as a browser configuration choice and verify the resulting target behavior in the same profile.
When an existing profile needs a proxy change, close it first. AdsPower's editing guide explicitly says to close a profile before changing profile settings. After saving the change, open the profile and repeat both checks. Do not continue a stateful workflow across an unverified route change.
Diagnose the failing phase
| What you observe | Inspect first | Next action |
|---|---|---|
| Paste format is not accepted | Delimiters and field order | Use IP:port:username:password or enter the four fields explicitly |
| Check Proxy fails | Protocol, host, port, and credentials | Confirm the endpoint outside AdsPower, then retry with matching fields |
| Check Proxy passes but target fails | Final URL, target status, account state, and target policy | Record a target failure separately from the route result |
| The profile opens with an unexpected IP | Selected Saved Proxies record and route policy | Recheck the saved record and profile assignment |
| Several profiles change IP together | Shared mobile proxy and Change IP URL | Pause the group, refresh deliberately, and recheck each profile |
| A proxy change does not take effect | Whether the profile was still open | Close it, edit, save, reopen, and run both checks again |
Close the profile from AdsPower's interface when the test or authorized workflow is complete. Retain only redacted evidence: profile identifier, proxy type, phase, observed result, target host, and timestamp. A proxy and a browser fingerprint do not grant permission to access a target; follow the target's terms and request limits.