This endpoint retrieves the complete detail record for a single electronic invoice identified by its invoice number. The response includes the issuing company’s information, the full customer profile, the numbering range used, the bill object (containing the CUFE hash, QR code URL, and a base64-encoded QR image), the line items with calculated taxes, and any associated withholding taxes, credit notes, or debit notes.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/tutosrive/factus_challenge/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
GET /factura/:number
Path Parameter
The full invoice number as assigned by the Factus API (e.g.,
SETP990000009). This is the number field returned in the list response or in the response body after creating an invoice.Request
No request body is required. The backend internally forwards thenumber path segment to GET /v1/bills/show/{number} on the Factus API, attaching the Bearer token from the server environment.
Response
200 — Success
Returns a JSON object whosedata property contains the full invoice detail.
Always
200 on success.Always
"OK" on success.Full invoice detail object.
404 — Not Found
When the invoice number does not exist on the Factus side, the upstream API returns an error response that the backend will surface as a 409 CONFLICT (see below) or a 500, depending on the error type. Factus itself does not return a distinct 404 HTTP status — the backend maps all non-"OK" upstream responses to 409.
409 — Conflict
Returned when the Factus API responds with an unexpected status value.500 — Internal Server Error
Two distinct shapes are possible: Shape A — upstream call failure (fromrequest_fact internal catch):
message (Axios error message), code (Axios error code), error_name (error class name).
Shape B — controller-level exception:
The
messaje key (with a j) in Shape B is a known typo in the backend source. Shape A uses error as a plain string ("ERROR INTERNO").