Inicio  |  Emisión  |  Web Services  |  Web Service CFDI 3.3  |  obtenerDatos
La LCO fue actualizada por última vez el 24/nov/2024

Method: obtenerDatos (get data)

The Webservice CFDI33 obtenerDatos method retreives data from an invoice using either the commercial folio and serie or the UUID as search criteria.

  1. Search criteria may be:
    • UUID only or
    • Commercial folio and serie
  2. A field is required if thus stated in column "Required":
    • Yes: this field is required.
    • No: this field is not mandatory.
    • Conditional: this field may be required or not, depending on other fields.

Method parameters:

Name Description Required
usuario

xs:string

Registered username.

Yes
password

xs:string

Username's password.

No
uuid

xs:string

The fiscal identifier of this invoice.

Conditional
folio

xs:long

The commercial number of this invoice.

Conditional
serie

xs:string

The serie fo this invoice

Conditional

Request example

Download this example

Returns

The method returns a compound type: obtenerDatosResponse, whose fields ared described in the following table:
obtenerDatosResponse's fields
Name Description Required
estatus

xs:int

The operation's status code. See the list Operation's status codes or a description of each code.

Yes
mensaje

xs:string

Response message, describing the operation's status.

Yes
comprobante

Compound type comprobante
Fields are describe in table "comprobante fields".

Yes

comprobante fields

Name Description Required
folio

xs:long

The commercial number of this invoice. Ejem: 525

Yes
nombreSerie

xs:string

CFDI's commercial serie. Ejem: SJ

Yes
regimenFiscal

xs:string

Fiscal regime's code of this invoice's issuer, according to the SAT catalogues.

Yes
lugarExpedicion

xs:string

Zip code of the location where this invoice was issued.

Yes
formaPago

xs:string

Form of payment (check, credit card, cash, etc) code of this invoice's products and/or services, according to the SAT catalogues.

Yes
metodoPago

xs:string

Method of payment (single payment, payment in installemtns, etc) code of this invoice, according to the SAT catalogues.

Yes
monedaNombre

xs:string

Name of this invoice's currency (Mexican Peso, Yen, US Dollar, etc).

Yes
monedaSimbolo

xs:string

Currency code of this invoice, according to ISO 4217.

Yes
notas

xs:string

Invoice's notes for additional info.

Yes
etiquetaComprobante

xs:string

Type of this invoice (Factura ->Invioce, Prefactura -> Pre-invoice, etc).

Yes
selloDigital

xs:string

The digital seal of this invoice, created using the issuer's digital seal certificate. It serves as the digital signature of the issuer for this invoice.

Yes
cadenaOriginal

xs:string

String of characters formed by the entire data of this invoice.

Yes
numeroSerieCsd

xs:string

Serial number of the digital seal's certficate.

Yes
version

xs:string

Invoice version.

Yes
fechaEmision

xs:dateTime

Invoice issuing date.

Yes
fechaPago

xs:date

Invoice date of payment.

Yes
importeDescuentos

xs:decimal

Total discount amount of this invoice.

Yes
importeTotal

xs:decimal

Total amount of this invoice.

Yes
subtotal

xs:decimal

Subtotal amount of this invoice.

Yes
monedaTipoCambio

xs:decimal

Exchange rate to Mexican Pesos of the invoice currency.

Yes
cancelada

xs:boolean

Indicates whether this invoice is canceled.

Yes
emisor

Compound type emisor

Contains the invoice issuer's information.

More info

Yes
receptor

Compound typereceptor

Contains the invoice receiver's information.

More info

Yes
timbradoInfo

Compound typetimbradoInfo

Contains the invoice's digital stamping information.

More info

Yes
concepto

Compound type concepto

Contains information for every product/service of this invoice.

More info

Yes
cfdiRelacionado

xs:string

Cadena del CFDI relacionado con este CFDI.

No
xml

xs:base64Binary

Arreglo de bytes que conforman el CFDI.

Yes

Response example

Download this example

Operation's status codes

More detailed descriptions may appear in mensaje field

200 — Process successful.
500 — The process could not be finished due to errors. Please retry.
501 — Failed attempting to connect to Database. Please retry.
502 — Failed attempting to store or retrieve data from Database.
503 — The maximum number of concurrent Database access attempts has been reached.
601 — Authentication error, please verify your credentials.
602 — This account is blocked.
603 — The account's password has expired.
604 — The maximum number of retry attempts due to failed authentication has been reached. The account will be blocked.
610 — The requested action is not supported in you implementation because either the implementation is not yet configured for such an action or is not possible its accomplishment. For the importar method this means your implementation has no connector configured yet.
611 — One or several required fields are missing in the request.
612 — Malformed file. The file format is different to the one expected.
613 — The numeric sequence has reached the end.
620 — You do not have permission to do this action.
621 — Invalid field.
622 — Unsupported action.
623 — Data not found.
624 — Uniqueness restriction violation.
625 — This action cannot be completed because it requires a previous action to complete.
626 — Implementation's configuration error.
630 — Your implementation's contract has expired.
631 — Your contract's payment date has passed.
632 — The maximum number of usage attempts for this implementation has been reached.
633 — This implementation is inactive.
Datos de contacto
comments powered by Disqus