Portal
v1.1.0
POST/v1/screen/legal

Screen a subject — Legal / lawsuits

Court / demandas case screening. Screens a subject against the published `legal` index. Each match is the indexed document (`_source`) minus search helpers. Photos and links are never stored or returned. Each call generates an immutable `audit_ref` retrievable via the portal audit API. **Auth:** API key in the `apikey` header. **Rate limits:** Enforced by Kong per plan tier. The `legal` endpoint searches `actor` and `demandado` name fields (court / demandas mid/src contract). **Name order (cname / icname):** Court records often store the same person with given names first (e.g. `JUAN JOSE FRANGIE SAADE`) or surnames first (e.g. `FRANGIE SAADE JUAN JOSE`). Send either form in `full_name` once — exact and fuzzy search both orderings on each party field, matching legacy ServiceNLF crudo behavior (actor/demandado × cname/icname). Names with fewer than three tokens are searched as provided only.

Clave de API — encabezado `apikey`

Cuerpo de la solicitud

application/json

Name only
Cargando…

Respuestas

Screening complete

Respuesta 200 — ejemplo
Cargando…
Pruebe esta solicitud

Copie un ejemplo en el lenguaje que prefiera. Reemplace los marcadores con sus credenciales.

curl -X POST 'https://screening-api.searchlook.mx/v1/screen/legal' \
  -H 'Content-Type: application/json' \
  -H 'apikey: sl_live_YOUR_KEY' \
  -d '{"full_name":"AGUILAR ARREOLA MARIA CONCEPCION"}'
Respuesta de ejemplo
200 OK
Cargando…