Return to a workflow
Reuse a saved profile when a task needs the browser context from an earlier session. Check that the target site's login is still valid before continuing.
Cloud Browser API
Cloud Browser API. Keep the context for your next session.
Save a browser profile, launch it with your proxy, and pick up the workflow in a live viewer. Stop the runtime when you are done; keep the profile for later.
01 / OVERVIEW
What is Cloud Browser API?
AdsCrawl Cloud Browser API manages saved browser profiles separately from running browser sessions. It supports starting and stopping a profile through the API and opening an interactive viewer while the browser is running. A stopped profile can be reused without keeping a browser running between tasks.
02 / USE CASES
Where it fits
Inspect the live page
Open runtime.connectUrl while signed in to view and interact with the browser. Viewer access uses a login session, not a public API-key URL.
Separate browser contexts
Keep distinct profiles for workflows that need separate cookies and proxy settings. Saved profile capacity and simultaneous runtime capacity are different limits.
03 / QUICKSTART
Start with one complete workflow
- Create an account and check the paid plan and Cloud Browser running allowance.
- Set ADSCRAWL_API_KEY on the server and replace the sample proxy with a valid proxy you control.
- Launch once, retain the returned browser id, and open runtime.connectUrl while signed in.
- Call stop when finished and query the detail endpoint until runtime.status is stopped.
Requires Bash and cURL. Set the ADSCRAWL_API_KEY environment variable on your server first.
Full request and response reference →# Replace the proxy address with your own proxy.
curl --fail-with-body -sS --max-time 200 \
-X POST "https://api.adscrawl.net/cloud-browsers/launch" \
-H "x-api-key: $ADSCRAWL_API_KEY" \
-H "content-type: application/json" \
-d '{
"proxy": { "server": "http://proxy.example.com:8080" },
"tabs": ["https://www.adscrawl.net"]
}'
# Open runtime.connectUrl from the response.
# When finished, replace <browser-id> with the returned id.
curl --fail-with-body -sS -X POST \
"https://api.adscrawl.net/cloud-browsers/<browser-id>/stop" \
-H "x-api-key: $ADSCRAWL_API_KEY"
# Confirm runtime.status is "stopped"; otherwise query/retry stop.
# Closing the viewer does not stop billing.
# If launch fails, inspect its returned id; do not repeat launch.- Free can save a profile, but launching a Cloud Browser requires a paid plan. Consult your account for actual running limits.
- Every API-key start requires an explicit valid proxy object. A saved proxy or countryCode alone is not a substitute.
- Closing the viewer does not stop runtime charges. A stop response may mean stopping; confirm the final stopped state.
- Launch creates a new profile. If it fails, inspect the returned id and clean up that browser instead of repeating launch blindly.
- For a temporary scripted Playwright session, use Remote CDP. It has a separate API and lifecycle.
Keep API keys on the server. For HTTP 402 check your balance; for 429 reduce concurrency and retry with backoff.
05 / FAQ
Common questions
Does a saved profile keep using a running slot?
A stopped profile does not occupy a running slot. It still counts toward saved profile capacity. Stop a running browser explicitly after use.
Can I keep a login forever?
No. Profile reuse does not override the target website's cookie expiration, sign-in policy or session revocation. Check the current state before running a task.
Can I use an API key in the viewer URL?
Viewer access requires a login session. Keep API keys on your server and use the documented authentication for each endpoint.
