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

Autofactura.notificaTicketsFacturados

Receive a list of the tickets that will be notified as invoiced and return a list with the ticket number, its status, and the notification process message.

Parameters of the notificaTicketsFacturados

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

Name Description Requested
clientId

xs:string

Username registered for use of the WebService.

Yes
password

xs:string

User password.

Yes
tickets

xs:string array

List of tickets to consult.

Yes

Example of a request

Download this example

Return

The method returns a list with the details of the process for each of the tickets.

Atributos de notificaTicketsFacturados
Name Description Requested
status

xs:string

Ticket status.

Yes
mensaje

xs:string

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

No
rNotificacion

tns:resultadoNotificacion

Object consisting of a status(int), message(String) and the ticket number.

No

tns:resultadoNotificacion

Name Description Requested
status

xs:string

Ticket status.

Yes
mensaje

xs:string

Ticket message.

No
noTicket

xs:int

Ticket number.

No

Example response - notificaTicketsFacturados

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.
Datos de contacto
comments powered by Disqus