How to Set Up Screenshot Alerts for an Indian Court Website

To set up screenshot alerts for an Indian court website, first decide whether you need a case-specific update or a visual change on a particular webpage. For case status, orders, judgments, or cause lists, start with the official eCourts gateway and its linked court services. For a page that lacks a suitable case alert, add its exact URL to a visual monitoring service, select the relevant page area, choose a restrained checking schedule, and enable a notification channel. Treat each alert as a prompt to verify the official record, not as confirmation of a legal event.

1. Choose the right kind of alert

Case information and webpage changes are different monitoring problems. If you are following a case, use the official court service where possible. The e-Committee describes finding daily orders and final judgments using identifiers such as CNR number, case number, court number, party name, or order date. The eCourts gateway also links to High Court and District Court services, case status, cause lists, orders, and judgments.

If you need to know when a public webpage itself changes—for example, a notice list or a page that does not offer a suitable case alert—a visual monitor can compare captures of that page over time. A changed screenshot only tells you the page appeared different to the monitor. It does not establish why it changed, whether a change is legally significant, or whether the page is the complete official record.

Check official options first

Open the official eCourts gateway and select the relevant High Court or District Court service.
For orders and judgments, check whether you can search using the available case identifiers. The e-Committee lists CNR, case number, court number, party name, and order date.
Consider the official eCourts mobile app. Its help guide describes selecting High Court, District Court, or both; its FAQ covers case information, orders, judgments, and court services.
The official portal also advertises an SMS route for case status using a CNR number. Check the portal for the current instructions.

The reviewed official sources do not establish that every court offers an alert for every webpage change. A screenshot alert is an optional way to notice a public page change, not a replacement for court-issued notices or authoritative case records.

2. Set up a visual monitor for a court webpage

The workflow below follows the capabilities documented by Visualping and Distill. These are optional third-party services; this guide does not claim either was tested against an Indian court website. Exact controls, available alert channels, and schedules can depend on the service, mode, and plan.

Copy the exact page URL. Use the page that contains the notice, cause-list entry, or document listing you care about. A monitor on a general homepage may not detect a change on a deeper page.
Add it to a visual monitoring service. In Visualping, add the webpage. Distill documents adding a monitor from the page as well.
Select the scope. Choose the whole page or the specific region containing the relevant list or notice. A focused region can avoid alerts caused by unrelated page changes.
Set a change criterion if available. Describe the change that matters, or configure the monitor to compare the selected area. Review the service’s own options for your chosen mode.
Choose a checking schedule and mode. Local monitoring runs from a browser or device; cloud monitoring runs independently of your browser where supported. Set an interval that fits your need, and follow the court website’s rules. The research sources establish no universal safe polling interval for Indian court sites.
Enable a supported notification channel. Visualping describes desktop notifications for local monitoring and email and other routes for cloud monitoring. Distill documents notification choices too, with availability dependent on subscription. Confirm that the channel you need is available in the selected mode and plan.
Review the first capture. Make sure the URL, page state, and selected area show the content you intend to track. If the initial capture is wrong or empty, fix that before relying on later alerts.
Verify every consequential alert. Open the official court page directly, confirm the date and content, and consult the official case record for decisions that matter.

Visualping documents whole-page or selected-area monitoring, scheduled checks, notifications, and visual comparisons. Distill documents page or region selection, local and cloud approaches, and notification options. Availability and configuration can change, so consult each service’s current documentation while setting up a monitor.

3. Choose the page area and alert schedule

Monitor the smallest useful region

For a long page, select the notice panel, document list, or other section that contains the update you need. This is a practical recommendation based on the documented whole-page and region-selection features: fewer unrelated changes can make alerts easier to interpret. If the relevant content moves or the page layout changes, revisit the selection and baseline capture.

Use a restrained checking interval

Choose an interval appropriate to how often you need to notice changes. The available research does not establish one interval as safe or suitable for every Indian court website. Visualping says its crawlers work at low frequency and do not attempt to solve CAPTCHAs or bypass protective systems; that is the vendor’s stated practice, not a permission guarantee or promise that a court page will work with the service. Follow the site rules and do not work around access controls.

Choose local or cloud monitoring deliberately

A local monitor depends on the browser or device being available according to that service’s design. A cloud monitor can run independently of your browser, where the service supports it. Select the mode based on the service’s current documentation and your need for continuous checks or a particular notification route. Do not assume that every notification method is available in every plan.

4. ScreenshotNeo API option for scheduled captures

If you are building your own workflow and need to capture a page on a schedule, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. A single GET request returns an image or PDF; your scheduler or application can store and compare the resulting captures. This API call captures a page—it does not by itself create a recurring schedule or send court alerts. You must build that surrounding workflow, and verify any consequential change against the official court source.

Get an access key and see the ScreenshotNeo API documentation. This example saves a capture of the target page:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://ecourts.gov.in/ \
  -o court-page.webp

Choose the exact court page you intend to monitor. The gateway URL above is only an example target; use the appropriate court service or public notice page for your workflow.

Automate comparisons carefully

For a recurring capture workflow, schedule requests at an interval consistent with the target site’s rules, retain a known baseline, and compare each successful capture with the prior one. Decide what counts as a meaningful change, such as a changed notice region, before notifying anyone. Keep the official URL and capture time with each result. A screenshot comparison can produce false alerts when layout, dates, rotating content, or other unrelated page elements change; it can also miss updates if the selected target is wrong or the page does not render in the capture.

Or skip the browser setup

Use ScreenshotNeo when you want a screenshot without configuring a browser capture stack. Its API accepts a URL in one request, and its other options include selected-element capture, full-page capture, waiting for a selector or network idle, custom CSS, JavaScript, cookies, headers, caching, and asynchronous jobs. The API can also be used from an MCP client by AI agents.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://ecourts.gov.in/ -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://ecourts.gov.in/"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://ecourts.gov.in/' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 screenshots. Yearly billing gives two months free, and every feature is available on every plan. See the API documentation for parameters and response details.

5. Troubleshooting missed or noisy alerts

Symptom	Likely cause	What to check
Alerts fire for irrelevant changes	The monitor compares unrelated areas or the page changes for reasons unrelated to the notice.	Narrow the selected region or adjust the change criteria. Review the comparison image to identify the changing element.
No alert arrives	The monitor may be inactive, the URL may be incorrect, the channel may be disabled, or the page may not be accessible in the selected mode.	Confirm the monitor is active, reopen the exact URL, check notification settings, and inspect the latest capture.
The first capture is blank or incomplete	The selected URL or mode may not render the intended content, or the monitor may have captured an unexpected page state.	Open the URL directly, confirm the correct court page, and review local or cloud mode support. Do not rely on alerts until the baseline is correct.
The notice changed but no alert appeared	The monitor may be watching the wrong page or region, or the change may not be visible in its capture.	Check the official page, inspect the capture and selected region, and update the monitored URL or area if needed.
Alerts stop after working initially	The monitor or notification channel may have been disabled, or its access to the page may have changed.	Check monitor status and channel settings, then review the most recent capture and service status information.
A CAPTCHA or access restriction appears	The site is applying an access control or protection.	Do not attempt to bypass it. Use the official court service or another permitted route, and follow the site’s rules.

6. Reliability, privacy, and cost considerations

Verify against the official record. A third-party visual monitor reports a detected page difference. It cannot confirm legal meaning, completeness, or official status.
Expect rendering limits. Results depend on the exact URL, page rendering, chosen region, and local or cloud mode. A page that changes dynamically may not be represented reliably in every capture.
Avoid aggressive checks. No universal safe interval was established by the reviewed sources. Follow the court site’s terms and avoid bypassing protective systems.
Account for service configuration. Monitor frequency and notification choices may depend on the tool, mode, and plan. Check current vendor documentation rather than assuming an option is included.
Budget for the whole workflow. Third-party monitor pricing was not established by the research used for this guide. If you use the ScreenshotNeo API, its stated plans are Free for 1,000 shots monthly, Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free. You still need a scheduler and comparison or alert logic for recurring monitoring.
Protect case-related information. Prefer public pages and avoid sending sensitive personal or case data to a service unless its handling is appropriate for your use. Keep API keys private if you automate captures.

Frequently asked questions

Can a screenshot alert tell me that a court order has been issued?

It can indicate that a monitored page looks different. Confirm an order through the official court service or record using the relevant case details.

Should I monitor the court homepage?

Only if the information you need appears there. For a notice or cause list on a deeper page, monitor that exact public page or use an official case-specific route.

Do I need an alert service if the case has a CNR number?

Check the official eCourts case-status and order routes first. The portal advertises an SMS case-status route using a CNR number, and the official app is another access option.

Does the ScreenshotNeo request send an alert automatically?

No. It returns a capture. A recurring alert workflow needs a scheduler, comparison logic, and a notification method that you configure.