Monitor API provides two ways to look up a single damage survey — by its auto-incremented integer ID, or by the related siniestro number. Both routes are protected by Bearer token authentication and available to all authenticated roles.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/sheeplettuce/Monitor/llms.txt
Use this file to discover all available pages before exploring further.
The
/siniestro/:no_siniestro route is registered in Express before /:id in the route file, so it is matched first and the two routes never conflict. Always use the explicit /siniestro/ prefix when looking up by claim number.Get by ID
levantamiento_concepto array and the related expediente.
Path Parameters
The numeric primary key of the levantamiento. Must parse as a valid integer.
Request Example
Response
200 — Success
Returns the matching levantamiento object with nested concepts and expediente.Error Responses
| Status | Body | Description |
|---|---|---|
400 | { "error": "id inválido" } | The :id path segment is not a valid integer. |
401 | — | Missing or invalid Bearer token. |
404 | { "error": "Levantamiento no encontrado" } | No levantamiento exists with that ID. |
Get by Siniestro Number
id is returned.
Path Parameters
The siniestro (claim) number to look up. Must match the
no_siniestro field on a levantamiento record.Example: SIN-2024-001Request Example
Response
200 — Success
Returns the most recent levantamiento for the given siniestro number, with nestedlevantamiento_concepto.
Error Responses
| Status | Body | Description |
|---|---|---|
401 | — | Missing or invalid Bearer token. |
404 | { "error": "No existe levantamiento para este siniestro" } | No levantamiento is linked to the provided siniestro number. |