Judicial records search
Search the Mexican Judicial Bulletin by name or legal name. You get the case files published by state and federal courts, in seconds.
State and federal court files, searched by name.
Singula searches the Judicial Bulletin by name or legal name and groups the case files by person. Shared names arrive flagged with how many people share them. Every result carries its source and its date.
One name can belong to several people. Every match arrives with a count of how many share it, and partial matches come back separate from exact ones.
What the search covers
The Mexican Judicial Bulletin is the source, and it is named in every response.
State and federal
Both jurisdictions fall inside one query, without asking a state at a time.
People and companies
For an individual the search runs on the given name and surnames exactly as you registered them. In a company we search the registered legal name and the trade name in a single query.
Case files and rulings
Every case file names the court and the state where it is heard, with the parties to the matter.
How it works
The search runs on a customer registered in your dashboard.
You pick the customer
The query is built from the data registered in the customer file.
We search the Judicial Bulletin
The search accounts for the variants a single name is published under and groups what belongs to one person.
The answer comes back in the same query
The verdict and the detail of every case file arrive together. Your log keeps the receipt with the exact date of the review.
An answer in seconds and the detail of every case file.
The verdict
Returns a clean result, medium risk or high risk, with the number of case files behind it.
A one-line summary
A ready-made sentence for your team’s review screen, with the count of cases behind it.
The other spellings
The variants the source published for that same person, listed in the same response.
Movements on the file
The dated text of every published ruling, from the first one to the most recent.
The litigation pattern
Who that person litigates against most, and which subjects their matters concentrate in.
An auditable search
Every query is recorded with its date, its source and its receipt.
The field-by-field detail is in the documentation.
What each result tells you
The response returns one of three levels, with the rule that triggers each one.
The customer name matches in full a person with several published case files.
The response includes every case file with its state, its counterparties and its dates.
The customer name matches, with fewer published case files behind it.
The detail of each matter comes in the same response, with its status and its dates.
The customer name does not show up in what has been published as of the date of the search.
The response records the source checked and the date of the review.
Scope and limits of the response
What the search returns and what stays with your organisation.
Index of the published record
What comes back are the case files exactly as they were published. The response carries the date the search ran. Where a process calls for an official certificate, the relevant authority issues it.
Name and identity
The search runs on the name. CURP validation against RENAPO runs on the same customer and confirms whose name the key is under.
Decision policy
The traffic light is a signal for your committee or for your risk manual. Who passes and who goes up for review is set by your organisation. Collecting the privacy notice and the consent of the person being searched falls to you as well.
The search is stored in the customer file.
Risk score
The search moves that customer’s score, alongside every other check you have already run.
One customer, every check
The same file supports CURP validation against RENAPO and RFC against the SAT.
Everything runs through the API.
Every operation on this page runs as an API call. The full field-by-field reference is in the documentation.
- Use it directly (the value in the body) or on a customer file. Same response.
# Persona física
curl https://api.singula.mx/app/judicial/customer/cus_lzk9m4ab3f \
-H "Authorization: Bearer sk_live_..."
# Persona moral
curl https://api.singula.mx/app/judicial-moral/customer/cus_9q2mv7xd1r \
-H "Authorization: Bearer sk_live_..."
→ {
"request_id": "6622f8a1c1d2e3f4a5b6c7d8",
"data": {
"status": "clean",
"total_records": 0,
"risk_level": "none",
"sources_checked": ["Boletin Judicial — Inteligencia de personas"],
"checked_at": "2026-07-28T10:31:00Z"
}
}Frequently asked questions
Yes. One query takes in both jurisdictions, and every case file names where it was filed, so the breakdown by state comes back in the same response.
An index of what has been published in the Mexican Judicial Bulletin. It is used to decide which customers go to a deeper review and to put on record that the review happened.
You cross-check against what you already know: the state, the period the cases span and the most frequent counterparties. CURP validation confirms the identity separately.
Everything arrives together, so your system resolves the review in a single step. Very common names take longer; allow up to a minute.
Every search leaves its receipt, its date, the source that was checked and the result that was delivered. All of it stays in the customer log.
This page is informational and is not legal advice. Searching a person's records means processing their personal data.
Try the judicial search
The test environment runs the whole flow at no cost. To move to production, you swap the key.