Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/CLINTONARMANDO/apiregistropendientes/llms.txt

Use this file to discover all available pages before exploring further.

A pendiente is the central resource of the system — a field work order assigned to one or more technicians. Each pendiente has a type (avería, instalación, traslado, etc.), a state lifecycle, and links to a client, location, and responsible employees. This page covers the core CRUD operations. For state transitions see State Management, and for type-specific data see Work Order Types.
All endpoints under /api/pendientes require a valid Authorization: Bearer <token> header. See Authentication for how to obtain a token.

​
GET /api/pendientes/

Retrieve a single work order by its internal ID.

​
Path parameters

​
id
number
required
The numeric ID of the pendiente.

​
Response — 200 OK

Returns a PendienteResponse object. See the filter endpoint for the full field list — the same structure is returned here.
cURL
curl --request GET \
  --url https://api.example.com/api/pendientes/42 \
  --header 'Authorization: Bearer <token>'

​
POST /api/pendientes/filtrar

Search and paginate work orders using any combination of filter criteria. Returns a Spring Page<PendienteResponse>. Pagination and sorting are controlled via query parameters on the URL. Filter criteria are sent in the request body.

​
Query parameters (pagination/sorting)

​
page
number
default:"0"
Zero-based page index.
​
size
number
default:"10"
Number of results per page.
​
sort
string
default:"fechaCreacion,desc"
Sort field and direction, comma-separated. E.g. fechaPendiente,asc or fechaCreacion,desc.

​
Request body (filter criteria)

​
clienteId
number
Filter to work orders belonging to a specific client ID.
​
usuarioId
number
Filter by the user (not employee) associated with the work order.
​
asignadoAId
number
Filter by the technician (employee ID) the work order is assigned to.
​
registradoPorId
number
Filter by the employee who created the work order.
​
estados
string[]
Filter by one or more states. E.g. ["ASIGNADO", "EN_PROGRESO"]. Valid values: REGISTRADO, ASIGNADO, EN_PROGRESO, PAUSADO, REVISION, POR_VALIDAR, OBSERVADO, FINALIZADO, POSTERGADO, CANCELADO.
​
estadosTecnico
string[]
Filter by one or more technical sub-states. Valid values: OK, PENDIENTE_PPPoE, PENDIENTE_VLAN, PENDIENTE_PPPoE_Y_VLAN.
​
fechaPendiente
string
Filter to work orders scheduled for a specific date (ISO 8601 datetime).
​
tipo
string
Work order type. One of: AVERIA, INSTALACION_INTERNET, INSTALACION_CAMARAS, RECOJO_DISPOSITIVOS, TRASLADO.
​
prioridad
string
Priority level. One of: BAJA, MEDIA, URGENTE, MUY_URGENTE.
​
lugar
string
Geographic zone. One of: ZONA_RURAL, JULIACA, PUNO, CHUCUITO, PLATERIA, ACORA, ILAVE, JULI, POMATA, CHACACHACA, YONGUYO, ZEPITA, DESAGUADERO.
​
titulo
string
Optional partial text search against the work order title/description.

​
Response — 200 OK

Returns a Spring Page wrapper with the following shape:
​
content
PendienteResponse[]
Array of work orders matching the filter criteria.
​
totalElements
number
Total number of records matching the filter, across all pages.
​
totalPages
number
Total number of pages.
​
number
number
Current page index (zero-based).
​
size
number
Page size used for this response.

​
Examples

curl --request POST \
  --url 'https://api.example.com/api/pendientes/filtrar?page=0&size=10&sort=fechaPendiente,asc' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "estados": ["ASIGNADO"],
    "lugar": "JULIACA"
  }'

​
POST /api/pendientes/

Create a new work order. The order is created in REGISTRADO state.

​
Request body

​
clienteId
number
required
ID of the client this work order is for.
​
tipo
string
required
Work order type. One of: AVERIA, INSTALACION_INTERNET, INSTALACION_CAMARAS, RECOJO_DISPOSITIVOS, TRASLADO.
​
prioridad
string
required
Priority. One of: BAJA, MEDIA, URGENTE, MUY_URGENTE.
​
lugar
string
required
Geographic zone where the work will be performed.
​
empresa
string
required
Company brand. One of: SIMAX, WINEX, OTRO.
​
direccion
string
required
Street address for the field visit.
​
fechaPendiente
string
required
Scheduled datetime in ISO 8601 format (e.g. 2026-06-15T09:00:00).
​
registradoPorId
number
required
ID of the employee creating this work order.

​
Response — 200 OK

Returns the newly created PendienteResponse object.
After creating a pendiente, create the type-specific details record (e.g. POST /api/pendientes/traslado) before assigning a technician. See Work Order Types.

​
Example

cURL
curl --request POST \
  --url https://api.example.com/api/pendientes/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "clienteId": 15,
    "tipo": "INSTALACION_INTERNET",
    "prioridad": "URGENTE",
    "lugar": "JULIACA",
    "empresa": "SIMAX",
    "direccion": "Jr. Lampa 340",
    "fechaPendiente": "2026-06-15T09:00:00",
    "registradoPorId": 3
  }'

​
DELETE /api/pendientes/

Soft-delete a work order. The record is not removed from the database; it is marked as deleted and excluded from normal queries.

​
Path parameters

​
id
number
required
The ID of the pendiente to delete.
This operation cannot be undone through the API. Contact your database administrator if you need to restore a deleted record.
cURL
curl --request DELETE \
  --url https://api.example.com/api/pendientes/42 \
  --header 'Authorization: Bearer <token>'

​
POST /api/pendientes/filtros

Returns the available enum options for filter dropdowns. Use this endpoint to populate UI filter controls dynamically rather than hard-coding enum values in the client.

​
Response — 200 OK

Returns an object with arrays of valid values for each filterable field.
​
estados
string[]
All valid EstadoPendiente values.
​
tipos
string[]
All valid TipoPendiente values.
​
prioridades
string[]
All valid PrioridadPendiente values.
​
lugares
string[]
All valid LugarPendiente values.
​
empresas
string[]
All valid EmpresaPendiente values.
cURL
curl --request POST \
  --url https://api.example.com/api/pendientes/filtros \
  --header 'Authorization: Bearer <token>'

Build docs developers (and LLMs) love

Get started for freeTalk to us