Skip to main content

Criminal Jurisdiction

Description​

The Criminal Jurisdiction service enables identity verification and screening against Chile's criminal records by full name. This service queries criminal jurisdiction cases involving penal law proceedings, including investigations, prosecutions, and trials for crimes defined under the Penal Code. Records provide access to procedural stage, case history, involved parties, and judicial rulings — critical for background checks, compliance, and risk scoring.

HTTP method POST​

Endpoint​

https://api.msla-id.com/experience-background-criminalrecord-api-v1/api/idv-govcheck/v1/cl-identity/criminal-jurisdiction
[SANDBOX Environment]

For testing purposes, use the base domain: apidev.msla-id.com

info

Before proceeding, make sure you have your jwt token, if you don't have it, check the login documentation.

Request header parameter​

NAMEREQUIREDTYPEDESCRIPTION
Authorization✅stringbearer jwt token
Content-Type✅stringapplication/json

Request body​

NAMEREQUIREDTYPEDESCRIPTION
fullName ✅stringFull name of the person. Must be between 3 and 200 characters.

Request body example​

{
  "fullName": "JUAN PEREZ GONZALEZ"
}

Status code responses​

CodeDescription
200 OK
400 Bad request
401 Unauthorized
404 Not found
500 Internal server error.

The full documentation error codes can be found here.

Response 200 status code​

[
  {
    "caseId": "Ordinaria-12-2026",
    "caseNumber": "2400123456-7",
    "court": "Juzgado de Garantia de Santiago",
    "caseName": "MINISTERIO PUBLICO C/ JUAN PEREZ GOMEZ",
    "entryDate": "15/01/2026",
    "caseStatus": "En tramitacion.",
    "defendant": "JUAN PEREZ GOMEZ",
    "history": [
      {
        "doc": "",
        "attachment": "",
        "type": "Resolucion",
        "observation": "Se resuelve solicitud.",
        "date": "20/01/2026",
        "status": "Firmada.",
        "statusChangeDate": "20/01/2026",
        "receptionDate": "",
        "georef": ""
      }
    ],
    "parties": [
      {
        "role": "Denunciado.",
        "name": "JUAN PEREZ GOMEZ",
        "freedomStatus": "Libre."
      },
      {
        "role": "Fiscal.",
        "name": "FISCAL GENERICO",
        "freedomStatus": ""
      }
    ],
    "relationships": [
      {
        "name": "PEREZ GOMEZ JUAN",
        "crime": "DELITO EJEMPLO.",
        "relationshipStatus": "En tramitacion.",
        "statusChangeDate": "15/01/2026"
      }
    ],
    "notifications": [
      {
        "type": "Mail.",
        "status": "Realizada",
        "executionDate": "20/01/2026",
        "hearingDate": "",
        "name": "FISCAL GENERICO"
      }
    ]
  }
]

Response structure notes​

  • data: array of criminal jurisdiction cases.
  • history: procedural history for each case.
  • parties: involved parties in the case.
  • relationships: related individuals and associated crimes.
  • notifications: notifications issued for the case.

Response 400 status code​

{
    "code": "IDV-1003",
    "message": "The fullName parameter is required"
}

Alternative 400 response when fullName is outside allowed length:

{
    "code": "IDV-1003",
    "message": "The fullName parameter must be between 3 and 200 characters"
}

Response 401 status code​

{
    "timestamp": "YYYY-MM-DDTHH:mm:ss.sssZ",
    "status": 401,
    "error": "Unauthorized",
    "path": "/api/idv-govcheck/v1/cl-identity/criminal-jurisdiction"
}

Response 404 status code​

{
    "code": "IDV-CL4001",
    "message": "No criminal jurisdiction cases found for the provided full name."
}

Response 500 status code​

{
    "code": "IDV-CL5001",
    "message": "An error occurred while retrieving criminal jurisdiction cases."
}