Autofactura.consultaTicketsFacturados
It receives a list of tickets to validate whether they have already been invoiced or not and returns a list with the status of each ticket.
- Parameters of the consultaTicketsFacturados
-
Name Description Requested clientId xs:string
Username registered for use of the WebService.
Yes password xs:string
User password.
Yes tickets Arreglo de xs:string
List of tickets to consult.
Yes
This method receives 3 parameters, of which are found in the SOAP message header.
Example of a request
Download this example
Return
- The method returns a list with the details of the process for each of the tickets.
-
Atributes of consultaTicketsFacturadosName 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 rConsulta Arreglo de tns:resultadoConsulta
Object consisting of a status (int), message(String) and the ticket number.
No -
tns:resultadoConsulta
Name Description Requested status xs:string
Ticket status
Yes mensaje xs:string
Ticket message
No noTicket xs:int
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 - consultaTicketsFacturados
Download this example
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.
