Inicio  |  Autofactura  |  Webservice Autofactura  |  Autofactura.getFacturados
La LCO fue actualizada por última vez el 03/abr./2026

Autofactura.getFacturados

It receives a date range from which you want to obtain the invoiced tickets and returns a list of tickets.

Parameters:

This method receives 4 parameters, 2 of which are found in the SOAP message header.

Name Description Requerido
clientId

xs:string

Username registered for use of the WebService.

Yes
password

xs:string

User password.

Yes
periodo

tns:periodo

Start and end dates of the consultation.

Yes
emisorId

xs:string

The issuer identifier.

Yes

tns:periodo

Name Description Requested
fechaInicial

xs:date

Initial date of the inquiry of invoiced tickets.

Yes
fechaFinal

xs:date

Fecha final de la consulta de los tickets facturados.

Yes

Example of a request

Download this example.

Return

This method returns a composite type: tns:ticketFacturado, the attributes are described in the following table:

Atributes of tns:ticketFacturado
Name Description Requested
status

xs:int

The operation status code. Response codes

Yes
mensaje

xs:string

The response message, a string of characters detailing the status of the operation.

Yes
ticketFacturado

Arreglo de tns:ticketFacturado

The query result may not be displayed if no tickets were found on the specified date.

No

tns:ticketFacturado

Name Description Requested
fecha

xs:dateTime

Date the ticket was invoiced

No
importeTotal

xs:decimal

Total ticket amount

No
ticketNo

xs:string

Ticket number

No
folioFactura

xs:long

The invoice number used to generate the ticket

No
serieFactura

xs:string

The series used to generate the invoice

No
uuidFactura

xs:string

The universal invoice identifier

No

Example response - getFacturados

Download this example.

Nota:

The "getFacturados" method returns only invoiced tickets by default.
If you want invoiced tickets to be included in global invoices, please contact support.

Response Codes

200 — Successful access: The client authenticated correctly and the method returned the results
In other words: any process which terminated without errors.
201 — Successful access: The client authenticated correctly and the method returned the results
In other words: any process which terminated without errors.
202 — This ticket had already been processed in a past import-transaction, this ticket already exists in a past transaction.
204 — There are errors regarding the validation of the ticket's verifier digit.
The verifier digit validation failed, this happened because either the ticket number does not comply with the verifier digit specifications or the generated SHA-1 hash is different.
206 — An invoice has already been created with this ticket.
208 — The ticket could not be stored and marked as an invoice.
The storage process found a problem and hence could not continue.
500 — Error found attempting to process the tickets.
Error found attempting to read the tickets' data.
601 — Client's authentication error.
Username / password incorrect.
Datos de contacto
comments powered by Disqus