Lawsuit monitoring
Discover new lawsuits against a CPF in up to 6 hours
Register a CPF once and Vigilant queries 12 Brazilian courts on regular cycles — 6h, 12h, daily or weekly. Email and webhook alerts when new cases, status changes, or new movements appear.
Why manual monitoring fails at scale
One-time searches become stale data
You approved a client in January with no cases. By March, they have 3 new labor claims and a tax-enforcement action. Without monitoring, you only find out when risk has already materialized.
Reviewing the full portfolio is infeasible by hand
1000 clients × 5 courts = 5000 queries. No team can repeat that weekly. In practice, portfolios stay weeks or months out of date.
Reactive alerts miss the commercial window
When you discover a new case via the press or a third party, it's usually too late to renegotiate a clause, demand collateral, or adjust scoring. Proactive monitoring buys decision time.
How it works
Register the CPF once
Via dashboard or API. Pick courts to monitor (1–12) and frequency (6h, 12h, daily, weekly).
First cycle creates the baseline
Vigilant runs the first full query and stores a snapshot. No alerts are triggered — you don't get an "alert storm" with the whole history.
Subsequent cycles detect changes
Each configured interval, Vigilant compares with the prior snapshot and fires alerts for: new cases, status change, new movements, party changes.
Alerts delivered via email and webhook
Configure recipients per monitor and integrate webhooks into internal systems (Slack, CRM, risk engine). Alerts are structured JSON, ready for automated processing.
Monitoring numbers
6h
Lowest alert latency
New case on the court → alert in ~6h
R$ 0.10
Per court per cycle
1 CPF × 5 courts daily = R$ 15/month
12
Courts monitored
State + federal covered
30–50%
Cache savings
Vigilant skips fresh data (<2d)
Register a CPF once and Vigilant queries 12 Brazilian courts on regular cycles — 6h, 12h, daily or weekly. Email and webhook alerts when new cases, status changes, or new movements appear.
Before vs after
- One-time query at approval
- Portfolio stale for months
- Reactive discovery via press/third parties
- Late renegotiation, no margin
- Risk concentrated at the wrong time
- Continuous post-approval monitor
- Portfolio always fresh (6h–7d)
- Alert before risk materializes
- Early action (collateral, scoring, renegotiation)
- Risk distributed in time and controlled
Integration ready for compliance and risk
Alerts delivered as standardized JSON, via webhook or email. Monitors can be created, paused and cancelled via API — integrates directly into risk engine, CRM or compliance systems.
Each monitor can have multiple recipients and one webhook. Pause or cancel anytime. Full docs at vigilant.trackjud.com.br/api/docs (Monitors section).
Frequently asked questions
You choose: 6h, 12h, daily or weekly. Faster frequencies cost more credits (full query per cycle). For most compliance cases, daily or weekly is enough — cases move on a scale of days, not minutes.
Daily × 30 days × 5 courts × R$ 0.10 = R$ 15/month per CPF. Weekly is R$ 2.15. For 1000 CPFs daily across 5 courts: R$ 15,000/month — but with smart caching (30–50% savings on fresh data), effective cost lands between R$ 7,500 and R$ 10,500.
The monitor auto-pauses. You receive an email notice. Buy more credits and monitoring resumes from where it stopped — it does not lose the snapshot or trigger "new case" alerts when resuming.
5 types detected: (1) new case — CPF appears in a case absent from the prior snapshot; (2) removed case — a previously visible case vanished; (3) status change; (4) new movements; (5) party change (someone entered/left). Each type has severity (critical, warning, info) and can be filtered at the webhook.
Yes. The alert includes the CNJ, class, subject, all parties, and the current movement state. To see specific filings (PDFs) or audit the full history, open the case on the court using the link included in the alert.
CNPJ monitoring is on the roadmap (release 2.2). Today the monitor is by CPF. Workaround: register the CPFs of the main partners + use CPF monitoring on them — covers most cases where risk first appears with executives before reaching the LLC/SA.
POST request with JSON payload (structure documented in api/docs). Exponential retry on 4xx/5xx from your end. HMAC-SHA256 signature via X-Vigilant-Signature header so you can validate authenticity. Idempotency key to avoid duplication.
Yes — accessed data is public from state courts. Vigilant is controller of its own logs and processor of your usage data. DPA available for Enterprise clients. For specific consent cases (e.g. monitoring an employee), consult your DPO before registering the CPF.
Start monitoring your portfolio today
5 free credits on signup. Test monitoring on 1 CPF for 7 days before scaling.