Certificates can also be managed through the obra-scoped endpoints (
GET /api/obras/{id}/certificates and POST /api/obras/{id}/certificates). The endpoints documented here operate across all obras in the tenant.List all certificates
Query parameters
Page number (1-indexed).
Results per page. Clamped between
1 and 500.Sort column. Accepted values:
obra (obra name), ente (contracting entity), monto, n_exp.Sort direction:
asc or desc.Full-text search across obra name, contracting entity, expedient number, status, month, amount, certificate number, invoice number, concept, observations, billing date, expiry date, and payment date. Diacritics are normalized.
Response
Paginated array of certificate objects joined with obra data.
- Request
- Response
Update a certificate
Core certificate fields (
n_exp, n_certificado, monto, mes, estado) are set at creation time through the obra-scoped endpoint and cannot be changed via this PATCH. The allowed fields are restricted to billing and payment tracking.Path parameters
UUID of the certificate.
Request body
Supply any subset of the following fields:Whether the certificate has been invoiced.
Invoice date.
Invoice number.
Invoice concept.
Whether payment has been received.
Free-text observations.
Payment due date.
Actual payment date.
Response
The full updated certificate row as stored in the database.
- Request
- Response
Delete a certificate
Path parameters
UUID of the certificate.
Response
Always
true on success.- Request
- Response
