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.

Each pendiente has a type, and each type has its own sub-resource with specialized fields. After creating a pendiente with POST /api/pendientes/, you must create the corresponding type details record before the order can be dispatched to a technician. All endpoints on this page are nested under the base path /api/pendientes and require a valid Authorization: Bearer <token> header.
PPPoE and VLAN fields are updated through dedicated sub-endpoints rather than the main PUT endpoint. This allows technicians to update connection credentials in the field independently of other record fields.

Traslado (relocation)

A traslado order covers moving a client’s ISP service to a new address — including migrating equipment and updating the network configuration at the destination.

GET /api/pendientes//traslado

Retrieve the traslado details for a pendiente.
id
number
required
ID of the pendiente.
Response — PendienteTrasladoResponse:
id
number
Sub-resource ID.
pendienteId
number
Parent pendiente ID.
lugarDestino
string
Destination zone (LugarPendiente enum).
direccionDestino
string
Full destination address.
tipoServicio
string
Type of service being relocated (TipoServicio enum).
ppoe
string
PPPoE username, populated after technician visit.
ppoePassword
string
PPPoE password.
vlan
string
VLAN tag assigned at destination.
cURL
curl --request GET \
  --url https://api.example.com/api/pendientes/42/traslado \
  --header 'Authorization: Bearer <token>'

POST /api/pendientes/traslado

Create the traslado details for an existing pendiente.
pendienteId
number
required
ID of the parent pendiente. The pendiente type must be TRASLADO.
lugarDestino
string
required
Destination zone. One of: ZONA_RURAL, JULIACA, PUNO, CHUCUITO, PLATERIA, ACORA, ILAVE, JULI, POMATA, CHACACHACA, YONGUYO, ZEPITA, DESAGUADERO.
direccionDestino
string
required
Street address at the destination.
tipoServicio
string
required
Service type to migrate. One of: INTERNET_FIBRA, INTERNET_INALAMBRICO, CAMARAS, DECOS, OTRO.
cURL
curl --request POST \
  --url https://api.example.com/api/pendientes/traslado \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "pendienteId": 42,
    "lugarDestino": "JULIACA",
    "direccionDestino": "Av. Manco Cápac 120, Juliaca",
    "tipoServicio": "INTERNET_FIBRA"
  }'

PUT /api/pendientes//traslado

Update the main traslado fields (destination address, service type, etc.).
cURL
curl --request PUT \
  --url https://api.example.com/api/pendientes/42/traslado \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "lugarDestino": "PUNO",
    "direccionDestino": "Jr. Lima 55, Puno",
    "tipoServicio": "INTERNET_FIBRA"
  }'

PUT /api/pendientes//traslado/ppoe

Update the PPPoE credentials after the technician has configured the connection at the destination. Both parameters are passed as query parameters.
ppoeUser
string
required
PPPoE username.
ppoePassword
string
required
PPPoE password.
cURL
curl --request PUT \
  --url 'https://api.example.com/api/pendientes/42/traslado/ppoe?ppoeUser=cli_12345678&ppoePassword=p%40ssword99' \
  --header 'Authorization: Bearer <token>'

PUT /api/pendientes//traslado/vlan

Update the VLAN tag assigned at the destination. The VLAN value is passed as a query parameter.
The source path for this endpoint contains a special character (¿) which may be a typo in the codebase. Verify the actual deployed path with your team if this endpoint does not respond.
vlan
string
required
VLAN identifier string.
cURL
curl --request PUT \
  --url 'https://api.example.com/api/pendientes/42/traslado/vlan?vlan=1042' \
  --header 'Authorization: Bearer <token>'

Build docs developers (and LLMs) love