🚨 India SEBI Enforcement Order Watch

SEBI enforcement orders as they are listed: adjudication orders, Chairman/Member orders, settlement orders and insider-trading orders, keyed on the source-native order id. LISTING SCOPE: date, order class, title and document link as published. It does not open or interpret the order document.

Output is one enforcement_order_record row per result; billing is pay-per-event, the value event being one enforcement order delta (a $0.02 start fee per run, then $0.10 per enforcement order delta plus one $0.10 source check per run that reads the source). Source: www.sebi.gov.in.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run k3CsiB6E3sRoyzebI on build 0.1.20 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

order_id	order_class	order_date_text	order_date	title	document_url
103018	adjudication	Jul 22, 2026	2026-07-22	Adjudication Order in the matter of Eastern Financiers Limited	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order
102994	adjudication	Jul 22, 2026	2026-07-22	Adjudication Order in the matter of Front Running of trades of Axis Mu	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order
102967	adjudication	Jul 20, 2026	2026-07-20	Adjudication Order in the matter of Central Depository Services India	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order
102916	adjudication	Jul 17, 2026	2026-07-17	[Corrigendum] " class='points'>Adjudication Order in respect of Sonia	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order
102867	adjudication	Jul 15, 2026	2026-07-15	Adjudication Order in respect of Jitendra Kumar Nahta HUF in the matte	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order
102855	adjudication	Jul 14, 2026	2026-07-14	Corrigendum Order In the matter of dealings in Illiquid Stock Options	https://www.sebi.gov.in/enforcement/orders/jul-2026/corrigendum-order-
102814	adjudication	Jul 14, 2026	2026-07-14	Adjudication Order in respect of Late Ms. Anju Rani in the matter of d	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order
102782	adjudication	Jul 13, 2026	2026-07-13	Adjudication Order in respect of Excel Technovation Pvt Ltd in the mat	https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order

The run finished with the status message: NORMAL: emitted 10 item(s)

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_key (string/null) — e.g. sebi:adjudication:103018
• order_id — e.g. 103018
• order_class — e.g. adjudication
• order_date_text — e.g. Jul 22, 2026
• order_date — e.g. 2026-07-22
• title — e.g. Adjudication Order in the matter of Eastern Financiers Limited
• document_url — e.g. https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order-in-the-ma
• scope_note — e.g. listing fields only; the order document is not opened or interpreted
• record_type (string) — e.g. enforcement_order_record
• delta_type (string/null) — null in every sample row

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "order_classes": [
    "adjudication"
  ],
  "pages": 1,
  "title_contains": [],
  "watch_mode": false,
  "baseline_id": "default",
  "max_items": 10
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.10 enforcement-order-delta = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
  "order_classes": [
    "adjudication"
  ],
  "pages": 1,
  "title_contains": [],
  "watch_mode": false,
  "baseline_id": "default",
  "max_items": 5
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
  "order_classes": [
    "adjudication"
  ],
  "pages": 1,
  "title_contains": [],
  "watch_mode": true,
  "baseline_id": "default",
  "max_items": 10
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.10 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

One real record from run k3CsiB6E3sRoyzebI, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_key": "sebi:adjudication:103018",
  "order_id": "103018",
  "order_class": "adjudication",
  "order_date_text": "Jul 22, 2026",
  "order_date": "2026-07-22",
  "title": "Adjudication Order in the matter of Eastern Financiers Limited",
  "document_url": "https://www.sebi.gov.in/enforcement/orders/jul-2026/adjudication-order-in-the-matter-of-eastern-financiers-limited_103018.html",
  "scope_note": "listing fields only; the order document is not opened or interpreted",
  "record_type": "enforcement_order_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 0
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each enforcement order delta is charged at the moment it is pushed (enforcement-order-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

Source

SEBI enforcement order listings (public, logged-out)

• https://www.sebi.gov.in/sebiweb/ajax/home/getnewslistinfo.jsp

Public, logged-out only — no API key, login, cookie or CAPTCHA.

Snapshot mode is a PREVIEW

watch_mode: false returns at most 25 records, hard-capped in code regardless of max_items, labeled output_mode: "preview". This cell sells change detection, not bulk record export.

Watch semantics

First watch run stores a private baseline and emits zero deltas. Later runs emit NEW / CHANGED / REMOVED keyed on the source-native id with before / after and changed_fields.

Source cadence

SEBI publishes orders with a real lag — on 25 July 2026 the newest adjudication order was dated 25 May 2026. An empty recent window is the source's cadence.

Terminal states

NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED. A zero with no evidence FAILS loud rather than exiting 0 quietly.

Preview vs Watch

• Preview (watch_mode: false): returns the current records as a capped snapshot, for a one-off look. Billed one source-check; no delta value event.
• Watch (watch_mode: true, the change feed): the first run seeds the baseline and emits 0 records (billed one source-check only); later runs emit one delta per change, each billed the value event. A run with no changes emits 0 and bills only the source-check.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.07
Enforcement Order Delta (enforcement-order-delta)	$0.10	$0.09	$0.08	$0.07

Worked at the live Free-tier price (watch mode, one delta per change):

• 8 enforcement order deltas: $0.02 start + $0.10 source check + 8 × $0.10 = $0.92
• 25 enforcement order deltas: $0.02 start + $0.10 source check + 25 × $0.10 = $2.62
• 400 enforcement order deltas: $0.02 start + $0.10 source check + 400 × $0.10 = $40.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: emitted 10 item(s). max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.sebi.gov.in. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.sebi.gov.in) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

Q: How many rows can one run return?
A: Up to max_items (default 400); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store (baseline_id names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other enforcement and sanctions watches actors?
A: Same output shape and billing model; this one covers www.sebi.gov.in. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (max_items) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
• First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

🔗 Related Actors

• EU Consolidated Sanctions Change Watch — Entity-level changes to the EU consolidated financial sanctions list (FSD): primary name, subject type, the regulation programmes an entity sits unde…
• Hong Kong SFC Enforcement News Watch — Securities and Futures Commission enforcement news as it is published: reprimands, fines, suspensions, bans, freezing orders and prosecutions, with t…
• US FDIC Bank Status Event Watch — Institution status as published by FDIC BankFind: active flag and end-of-existence date, so a change in standing is observable
• US HHS-OIG Exclusion Change Watch — Monthly additions to and reinstatements from the HHS-OIG List of Excluded Individuals and Entities (LEIE). OIG publishes the change files monthly and…
• US OFAC Sanctions Action Watch — OFAC Recent Actions as they are posted: the action's own identifier, its date, its headline and its category (Sanctions List Updates, Regulations and…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.