The Receipts API exposes read-only access toDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/GuillermoNavarro/Proyecto_comunidades/llms.txt
Use this file to discover all available pages before exploring further.
Recibo (receipt) records. Receipts are created automatically by the system whenever a new Cuota (fee) is saved — one receipt is generated per active user in the community (or for a single user when the fee type is INDIVIDUAL). There is no POST endpoint for manually creating receipts through this API.
Each receipt links a user to a fee and tracks whether the charge is PENDIENTE (outstanding) or PAGADO (paid).
Receipts cannot be created manually via the API. They are generated automatically when you call POST /api/cuotas.
Authorization header.
GET /api/recibos/me
Returns all receipts belonging to the currently authenticated user, identified by theid claim in their JWT.
Required role:
USER or ADMIN200 OK — array of Recibo objects for the calling user.
Unique identifier of the receipt.
Amount charged to this user on this receipt.
Payment status. Either
PENDIENTE (unpaid) or PAGADO (paid).The fee that generated this receipt. The
comunidad field is omitted from the nested cuota to avoid circular data.The community this receipt belongs to.
The user to whom this receipt is issued. The
password and comunidad fields are excluded from this nested object.Example response
| Status | Meaning |
|---|---|
200 | OK — list returned (may be empty). |
403 | Forbidden — caller does not have USER or ADMIN role. |
GET /api/recibos/comunidad
Returns all receipts (bothPENDIENTE and PAGADO) for the community encoded in the caller’s JWT. Useful for a full payment ledger view.
Required role:
ADMIN200 OK — array of Recibo objects scoped to the caller’s community (same schema as GET /api/recibos/me).
| Status | Meaning |
|---|---|
200 | OK — list returned (may be empty). |
403 | Forbidden — caller does not have ADMIN role. |
GET /api/recibos/comunidad/morosos
Returns only thePENDIENTE receipts for the caller’s community — the delinquency list. Use this endpoint to identify residents with outstanding balances.
Required role:
ADMIN200 OK — array of Recibo objects where estadoRecibo is PENDIENTE.
Example response
| Status | Meaning |
|---|---|
200 | OK — list returned (may be empty if no debts outstanding). |
403 | Forbidden — caller does not have ADMIN role. |
GET /api/recibos/usuario/{idUsuario}/pendientes
Returns allPENDIENTE receipts for a specific user within the caller’s JWT community. Useful for checking the total outstanding debt of an individual resident.
Required role:
ADMINPath parameters
The unique identifier of the user whose pending receipts should be returned.
200 OK — array of Recibo objects where estadoRecibo is PENDIENTE for the given user.
Example response
| Status | Meaning |
|---|---|
200 | OK — list returned (may be empty). |
403 | Forbidden — caller does not have ADMIN role. |
GET /api/recibos/cuota/{idCuota}
Returns all receipts associated with a specific fee within the caller’s JWT community. Useful for auditing payment status for a particular billing cycle.Required role:
ADMINPath parameters
The unique identifier of the fee whose receipts should be returned.
200 OK — array of Recibo objects for all residents linked to the specified fee, reflecting each individual’s payment status.
Example response
| Status | Meaning |
|---|---|
200 | OK — list returned (may be empty). |
403 | Forbidden — caller does not have ADMIN role. |