Beyond the required payment proof image submitted at request creation time, a service request can carry three additional file types: an optional customer attachment (for services that allow it), a fiscal invoice document uploaded by staff when the customer requested one, and a delivery confirmation document uploaded by staff when the service is completed. All uploaded files are saved toDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/SERVICIOS-BACK/llms.txt
Use this file to discover all available pages before exploring further.
wwwroot/uploads/service-requests/ on the server disk and are served as static files. Each uploaded file is stored with a UUID-prefixed filename to avoid collisions.
The payment proof image itself is not managed by these endpoints — it is uploaded separately via
POST /api/uploads/payment before creating the request. See Create & Retrieve for that flow.POST /api/servicerequests//attachment — Upload optional attachment
Uploads an additional file attachment to a service request. This is only permitted when the associated service hasPermiteAdjunto = 1 set in its service definition. The stored procedure CreateServiceRequestAttachment enforces this check and returns an error if the service does not allow attachments.
Authentication: Bearer token (any role)
Content type: multipart/form-data
Max file size: 10 MB
Accepted file types: Any (no extension restriction at the API layer)
Path parameters
The
requestId of the service request to attach the file to.Form fields
The file to upload. Must be non-empty and no larger than 10 MB.
Response
The auto-generated ID of the newly created attachment record.
Attempting to upload an attachment for a service that has
PermiteAdjunto = 0 will return an error from the CreateServiceRequestAttachment stored procedure. Check the permiteAdjunto field on the service request detail (GET /api/servicerequests/{id}) before showing the upload UI to the user.GET /api/servicerequests//attachment — Get attachment info
Returns the metadata of the optional attachment associated with a service request. Does not return the file content itself — use therutaArchivo path to construct the full URL for download.
Authentication: Bearer token (any role)
Path parameters
The
requestId of the service request whose attachment metadata you want to retrieve.Response
Returns404 Not Found if no attachment has been uploaded for the request.
Auto-generated attachment record ID.
ID of the parent service request.
Original filename as provided by the uploader.
Server-relative path to the file, e.g.
/uploads/service-requests/uuid_filename.ext. Prefix with the server base URL to build a download link.File size in bytes.
Timestamp when the file was uploaded.
POST /api/servicerequests//invoice — Upload invoice document
Uploads a fiscal invoice document for a service request that was created withrequiresInvoice = true. This is a staff-only action performed after the payment has been approved and the service is in progress.
Authentication: Bearer token — SUPER_ADMIN, ADMIN_GENERAL, or GESTOR_SUPREMO
Content type: multipart/form-data
Max file size: 10 MB
Accepted file types: .pdf, .png, .jpg, .jpeg
Path parameters
The
requestId of the service request to attach the invoice to.Form fields
The invoice file. Must be non-empty, no larger than 10 MB, and have an accepted extension (
.pdf, .png, .jpg, or .jpeg). Returns 400 Bad Request for any other extension.Response
Server-relative path where the invoice was saved, e.g.
/uploads/service-requests/uuid_invoice.pdf.POST /api/servicerequests//delivery-attachment — Upload delivery confirmation
Uploads a delivery confirmation document when a service request is completed. This can be a signed delivery receipt, a photo, or any supporting document in an accepted format. Authentication: Bearer token —SUPER_ADMIN, ADMIN_GENERAL, GESTOR_SUPREMO, or GESTOR
Content type: multipart/form-data
Max file size: 10 MB
Accepted file types: .pdf, .png, .jpg, .jpeg, .webp
Path parameters
The
requestId of the service request to attach the delivery document to.Form fields
The delivery confirmation file. Must be non-empty, no larger than 10 MB, and have an accepted extension (
.pdf, .png, .jpg, .jpeg, or .webp). Returns 400 Bad Request for any other extension.Response
Server-relative path where the delivery document was saved, e.g.
/uploads/service-requests/uuid_delivery.pdf.File storage
All files uploaded through these endpoints are saved to thewwwroot/uploads/service-requests/ directory on the server. Each file is renamed to {UUID}_{originalFilename} before saving to prevent collisions. The relative path stored in the database (/uploads/service-requests/...) can be prefixed with the server base URL to construct a publicly accessible download link, since the API serves static files from wwwroot.