Issuer / receiver technical standards

Requirements that the electronic issuer/receiver software must meet (Descripción Técnica Servicios Emisores Electrónicos, DGII). The registration/certification process, sequences, and environments are covered in the Authentication/Emission section of this API and in the DGII guide.

XML file naming

Character restrictions

In ALFANUM fields, escape: " → ", ' → ', < → <, > → >, & → & (also ©, €, ®). In the QR (URL), replace reserved characters with their hex equivalent (%20, %26, …). Do not include empty tags — they cause rejections.

XML signing

• SHA-256 algorithm; sign with preservewhitespace = false.
• The certificate's SN field must match the holder's RNC/Cédula/Passport.
• Once signed, the XML cannot be altered.

Services a receiver must expose

Same standardized path; only the host changes (published in the Directory). They must use HTTPS, standard ports, case-insensitive routes, and be reachable from the internet.

• Reception (mandatory) — POST /fe/recepcion/api/ecf (multipart/form-data, xml field) → returns the signed ARECF.
• Commercial approval (mandatory) — POST /fe/aprobacioncomercial/api/ecf (multipart, xml) → HTTP 200/400.
• Authentication (optional) — GET /fe/autenticacion/api/semilla + POST /fe/autenticacion/api/validacioncertificado → Bearer token for the endpoints above.

The reference XSDs are published by the DGII. The issuer must keep its services compatible over time.

More in the portal

• Interactive API reference
• Quickstart
• e-CF Overview
• Issuer / receiver standards
• e-CF Format reference