Best Screenshot API for Indian Real Estate Listing Websites
Compare screenshot APIs for Indian property listings, learn what documentation can and cannot prove, and run a site-specific pilot before choosing.
Short answer: start a controlled pilot with ScreenshotNeo, then compare it with ScreenshotOne, Browserless, and Urlbox using the actual property pages and locations you need. ScreenshotOne is the strongest documented candidate when India IP localization is a requirement: its documentation lists an India IP-country option using data-center proxies. That does not establish that it can reliably capture 99acres, Magicbricks, Housing.com, or any other specific portal. No cited vendor documentation proves that. Choose from measured results on your own URLs, not feature lists alone.
This guide explains what the available evidence supports, how to compare providers, and how to build a reproducible pilot. The cited sources are official product documentation. Capabilities and prices can change; verify them before committing.
1. What the available evidence says
| Option | Documented evidence relevant to this use case | What remains unknown |
|---|---|---|
| ScreenshotNeo | Screenshot API with image or PDF output, full-page and element capture, wait controls, custom headers and cookies, device settings, caching, bulk capture, and other options. It also removes known consent banners, newsletter popups, and chat widgets before capture; individual steps can be disabled. Clean shots alone are billed, and responses indicate page verdict and billing status. | The supplied product facts do not establish capture success on any named Indian property portal or an India IP routing option. Test your pages and localization requirements. |
| ScreenshotOne | Its options documentation lists ip_country_code=in for India. The documented regional option uses data-center proxies and is not a residential proxy or stealth feature. It also documents GET and POST requests, access-key authentication, and image responses. |
India routing documentation does not prove successful capture of a named real-estate site. Confirm current pricing, quotas, and behavior in your own pilot. |
| Browserless | Its REST screenshot documentation describes PNG, JPEG, and WebP, full-page and viewport capture, clipping, device scale, element selection, and scrolling to trigger lazy-loaded content. | The cited documentation does not establish India-specific routing or results on property portals. |
| Urlbox | Its documentation describes rendering URLs and HTML into screenshots, PDFs, and videos, plus extraction of text, HTML, and metadata. | The cited overview does not establish India IP routing or tested support for named listing sites. |
| Self-managed Playwright | Playwright exposes browser screenshot capture, full-page capture, and format options. It is a useful baseline when you want to manage the browser yourself. | You own browser hosting, scaling, upkeep, and consistency. Results can vary across operating systems, browser versions, settings, hardware, power state, and headless mode. |
Sources: ScreenshotOne options, ScreenshotOne getting started, Browserless REST screenshot API, Urlbox documentation, and Playwright’s screenshot guide, Page screenshot API, and visual comparison guidance.
2. Choose by pilot results, not by a universal ranking
For Indian listing websites, ScreenshotNeo is the first API to try: consent banners, popups, and chat widgets are removed before capture, and only clean shots are billed. Include ScreenshotOne early when India IP localization is essential because it explicitly documents that option. Include Browserless if its capture controls fit your workload, and Urlbox as another hosted rendering candidate. This is a shortlist for a bake-off, not a claim that any provider wins on every portal.
The documentation does not establish reliable rendering on 99acres, Magicbricks, Housing.com, or other specific portals. A provider can support full-page capture and still miss content because a site requires a session, blocks automated traffic, delays images, or changes its page behavior. Test representative URLs before choosing.
3. Design a fair bake-off
- Choose representative pages. Include listing detail pages and search results from each portal you are permitted to access. Use stable, public URLs where possible, and record when a page requires login or has a consent state.
- Fix the capture conditions. Set the same viewport dimensions, device scale, output format, wait policy, and full-page or viewport mode across providers. Record whether the request is routed through India when that matters.
- Test page states. Include first visit and repeat visit, desktop and mobile viewports, pages with long image galleries, and pages that load content as the user scrolls. Do not assume scrolling or a full-page option will trigger every lazy-loaded image.
- Define success before running. For example, decide whether a successful screenshot must show the listing title, price, location, and first gallery image. Track missing or obscured content separately from transport-level request success.
- Repeat captures. Run each case more than once and at representative times. Record intermittent failures, elapsed time, response status, output dimensions, and provider billing or quota usage.
- Review terms and access limits. Use only access patterns permitted by each property portal and provider. The sources cited here do not establish the terms of 99acres, Magicbricks, or Housing.com.
| Measure | What to record |
|---|---|
| Capture success | Whether the image contains the required listing content, not merely whether the API returned an image. |
| Localization | Requested region, documented routing method, and observed page variation. An India IP option does not imply residential routing. |
| Completeness | Whether the gallery, price, map, and below-the-fold sections loaded as required. |
| Repeatability | Visual differences between repeated captures under the same settings. |
| Latency and capacity | Elapsed time, concurrency behavior, request limits, and timeouts at your expected load. |
| Economics | Billable successful captures, failed or blank results, cache hits, storage, and any required browser infrastructure. |
4. Set capture requirements for property pages
Viewport, full page, or a selected element
Use viewport capture when you need a consistent above-the-fold record, such as the price and initial gallery. Use full-page capture when the entire listing matters, but check whether the provider scrolls to load lazy images and whether the resulting image becomes too tall to review or store efficiently. Element capture can isolate a gallery, price panel, or listing card when the page layout is stable. Selectors can break when a site changes its markup.
Wait policy and lazy loading
Fixed delays are easy to understand but can waste time on fast pages and still be too short on slow ones. Waiting for a selector is more targeted when the selector reliably signals that the needed content exists. Network idle can be unreliable on pages with analytics or long-lived connections. For long galleries, verify the actual image content in the result; a page-load event alone does not prove that lazy images have loaded.
Consent, sessions, and overlays
Record whether the capture represents a first visit or an existing consent state. A banner may cover the price or gallery even when the page itself loads successfully. ScreenshotNeo removes 60+ known consent platforms as well as newsletter popups and chat widgets before capture; each step can be turned off. For other providers or custom overlays, check their documented controls and the result itself. Use cookies or authorization only when you are entitled to access that account or content.
Regional content and device behavior
Some pages vary by location or device. ScreenshotOne documents an India IP-country option using data-center proxies, and says it is not a residential proxy or stealth feature. Treat the selected region as one experimental variable: compare it with your normal route and inspect the resulting content. Set viewport and device scale explicitly so provider defaults do not make comparisons misleading.
5. Run a self-managed Playwright baseline
If you want to control the browser directly, Playwright provides a useful baseline. Keep the browser and operating system consistent between runs; its visual comparison guidance notes that these environment differences can change screenshots. The example below captures a page after a short wait and writes a full-page PNG.
import { chromium } from 'playwright';
const browser = await chromium.launch({ headless: true });
const page = await browser.newPage({
viewport: { width: 1440, height: 1000 },
deviceScaleFactor: 1,
});
try {
await page.goto('https://example.com/listing', {
waitUntil: 'domcontentloaded',
timeout: 45_000,
});
await page.waitForTimeout(1500);
await page.screenshot({ path: 'listing.png', fullPage: true });
} finally {
await browser.close();
}Install the package and browser in your project using the official Playwright installation guide. Replace the example URL with a page you are authorized to capture. This minimal script does not solve login, consent, lazy loading, access restrictions, retries, or storage; add those deliberately and measure them.
Direct provider examples
ScreenshotOne documents GET and POST request methods, access-key authentication, and image response content types. Keep the access key on a server, not in browser JavaScript or a public repository. Its official getting-started documentation has the current request parameters and examples; the dossier does not provide enough detail to responsibly invent a complete provider-specific request URL here. Browserless and Urlbox also have product-specific request formats; use their official docs linked above rather than guessing token or parameter names. For ScreenshotNeo’s supported parameters and authentication, use its API documentation.
6. Or skip the browser setup
ScreenshotNeo provides one GET request for an image or PDF, with controls for full-page or element capture, waits, device settings, custom headers and cookies, and more. Its 63 options include custom CSS and JavaScript, click and hide selectors, resource blocking, timezone and geolocation, resizing, caching, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, and a usage API. Every feature is on every plan. Check the ScreenshotNeo API docs for the full parameter list and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);Replace the sample URL with the target listing page. Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed; response headers identify the page verdict and billing status. An MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Other listed plans are Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000; yearly billing gives two months free. Test your target pages to confirm fit, especially if India-region routing is a requirement.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
7. Compare cost, performance, and reliability
Cost
Estimate cost from your own definition of a successful capture and expected volume. Include retries, cache behavior, concurrency limits, storage, and any browser infrastructure you operate. ScreenshotOne’s pricing page listed Basic at $17 per month for 2,000 screenshots and Growth at $79 for 10,000 when accessed in 2026; it says prices exclude VAT. These are volatile page values, not evidence of the cheapest overall service. Check the current ScreenshotOne pricing before comparing. ScreenshotNeo lists a free tier of 1,000 per month and paid plans beginning at $5 for 3,000; verify current plan details on its site.
Performance
For a pilot, measure end-to-end time from request to usable image, not just API response time. Full-page captures, high device scale, delayed content, and large galleries can increase processing and output size. If the same URLs recur, evaluate caching with an appropriate TTL and decide how fresh a listing screenshot must be. Batch or asynchronous capture can help larger workflows where supported, but account for job completion and webhook reliability.
Reliability and repeatability
Separate API availability from page-level success. Track timeouts, blank pages, bot checks, consent overlays, missing images, and incomplete results as distinct outcomes. Retry only transient failures, with a bounded attempt count and backoff; repeated retries will not fix a persistent access restriction or broken selector. For visual monitoring, pin browser and rendering settings and compare like with like. Do not treat provider documentation as a reliability guarantee for a target site.
8. Troubleshooting common capture failures
| Symptom | Likely cause | What to try |
|---|---|---|
| Screenshot is blank or mostly empty | Navigation did not complete, the page returned an empty state, or the target blocked or challenged the request. | Inspect the page verdict or provider response, open the URL in a normal browser, and distinguish a page failure from a capture failure. Do not assume retries bypass a site restriction. |
| Price or gallery is missing | Content loaded later, requires scrolling, or depends on client-side requests. | Wait for a meaningful selector, scroll the page to trigger lazy loading where permitted, and confirm the content appears before capture. |
| Consent panel covers listing details | First-visit consent state or a regional banner. | Decide whether the desired record includes that state. Use a documented consent-handling control, or ScreenshotNeo’s consent cleanup when appropriate; validate that the resulting page still represents the intended content. |
| Capture differs between runs | Dynamic ads, recommendations, image loading, location, cookies, or inconsistent browser environment. | Fix viewport, device scale, locale, timezone, wait condition, and browser version; block variable resources only if that matches the monitoring goal. |
| Element capture fails after a site update | The CSS selector no longer matches or matches multiple elements. | Inspect the current markup, choose a stable selector, and add a clear failure check when the element is absent. |
| Request times out | Slow page, overly strict wait condition, long-running network activity, or provider timeout limit. | Use a targeted wait instead of waiting for every connection to stop, increase the timeout within provider limits, and record slow pages separately. |
| Unexpected bill or quota use | Retries, cache misses, or a different provider definition of billable capture. | Check response usage fields and plan terms, add bounded retries, and compare billed usage with successful images. ScreenshotNeo responses include billing and page-verdict headers. |
| Regional content does not change | Target may not vary by IP, or routing behavior may differ from the assumed location. | Verify the provider’s documented routing behavior and compare observed content. An India IP option does not mean residential proxy access. |
9. Decision checklist
- Have you tested the exact property portals and page types you need?
- Does the required region mean an India data-center IP, a residential connection, or simply India-localized page content?
- Do the captures include the needed price, location, and gallery images?
- Are first-visit consent state, sessions, and login requirements handled appropriately?
- Can you meet latency and concurrency needs at expected volume?
- Have you compared successful captures and billed usage using the same workload?
- Have you reviewed the provider and target site terms for your intended use?
10. Frequently asked questions
Which API has documented India IP routing?
ScreenshotOne’s options documentation lists India as an IP-country choice using data-center proxies. This is evidence of a documented option, not a guarantee for any particular listing website.
Can I assume a full-page screenshot includes every property image?
No. Lazy-loaded images may need scrolling or additional waiting, and the final image should be checked for completeness.
Should I use a screenshot API or run Playwright myself?
Use a hosted API when you want a managed capture endpoint and its available controls. Run Playwright yourself when browser environment control and ownership justify maintaining the runtime. A small pilot can show which operational tradeoff fits.
Is there a proven best provider for 99acres, Magicbricks, or Housing.com?
The cited research contains no controlled results for these sites. The best choice remains unresolved until you test representative URLs under your intended conditions.
