emite.do SDK — Python
SDK oficial para api.emite.do. El mismo POST /api/v1/ecf cubre E31–E47.
Guía: docs.emite.do/sdks/python · API: docs.emite.do
Instalación
pip install ecfservice
Inicio rápido
from datetime import date
from ecfservice import ECFClient
with ECFClient(api_key="...") as client:
doc = client.ecf.create(
idempotency_key="INV-2026-0001",
ecf_type="31",
environment="TesteCF",
payload={
"Encabezado": {
"Version": "1.0",
"IdDoc": {
"TipoeCF": "31",
"eNCF": "E310000000001",
"FechaVencimientoSecuencia": "31-12-2028",
"IndicadorMontoGravado": 0,
"TipoIngresos": "01",
"TipoPago": "1",
},
"Emisor": {
"RNCEmisor": "130478031",
"RazonSocialEmisor": "Mi Empresa SRL",
"DireccionEmisor": "AV. DEMO 1",
"FechaEmision": date.today().strftime("%d-%m-%Y"),
},
"Comprador": {
"RNCComprador": "131098193",
"RazonSocialComprador": "Cliente SRL",
},
"Totales": {
"MontoGravadoTotal": 10000.0,
"MontoGravadoI1": 10000.0,
"ITBIS1": 18,
"TotalITBIS": 1800.0,
"TotalITBIS1": 1800.0,
"MontoTotal": 11800.0,
},
},
"DetallesItems": {
"Item": [
{
"NumeroLinea": 1,
"IndicadorFacturacion": 1,
"NombreItem": "SERVICIO DEMO",
"IndicadorBienoServicio": 2,
"CantidadItem": 1.0,
"UnidadMedida": "43",
"PrecioUnitarioItem": 10000.0,
"MontoItem": 10000.0,
}
]
},
},
)
print(doc.public_id, doc.status) # received — el veredicto fiscal llega después
doc = client.ecf.get(doc.public_id)
xml = client.ecf.download_xml(doc.public_id)
ecf_type acepta 31 32 33 34 41 43 44 45 46 47. Cambia TipoeCF y el e-NCF (E32…, E47…) al tipo.
Misma idempotency_key → 200 del original (el payload no se compara).
Builder
from ecfservice import ECFPayloadBuilder
payload = (
ECFPayloadBuilder(ecf_type="31")
.id_doc(eNCF="E310000000001", FechaVencimientoSecuencia="31-12-2028")
.emisor(RNCEmisor="130478031", RazonSocialEmisor="Mi Empresa SRL", FechaEmision="15-08-2026")
.comprador(RNCComprador="131098193", RazonSocialComprador="Cliente SRL")
.totales(MontoTotal=11800.0, TotalITBIS=1800.0)
.add_item({"NumeroLinea": 1, "NombreItem": "Servicio", "MontoItem": 10000.0})
.build()
)
Pone TipoeCF (no TipoEcf). FechaEmision va en Emisor.
Empresa, rangos, inbox
profile = client.client.company()
seqs = client.client.sequences(active_only=True)
inbox = client.client.inbox(acked=False)
client.client.ack_inbox(inbox.items[0].public_id)
Los rangos se listan; no se crean por API.
Comunicaciones Emite
Feed de avisos de soporte (GET /notices/changes). No es el calendario DGII
(client.dgii.status_maintenance()). Un feed vacío no resuelve nada; un
409 cursor_expired exige bootstrap de nuevo y retirar réplicas ausentes
sin marcarlas resueltas.
feed = client.notices.changes() # bootstrap
cursor = feed.next_cursor
later = client.notices.changes(cursor=cursor)
notice = client.notices.get(feed.changes[0].notice.id)
ACECF y ANECF
client.ecf.submit_acecf(
idempotency_key="ac-001",
encf="E310000000001",
rnc_emisor="130478031",
rnc_comprador="131098193",
fecha_emision="15-08-2026",
monto_total="11800.00",
estado="1",
)
client.ecf.cancel_sequences(
idempotency_key="an-001",
cancellations=[{
"ecf_type": "31",
"sequence_from": "E310000000010",
"sequence_to": "E310000000012",
"quantity": 3,
}],
)
Webhooks
Hoy el service notifica accepted, conditionally_accepted y rejected.
wh = client.client.create_webhook(
url="https://mi-app.example/webhooks/ecf",
events=["accepted", "conditionally_accepted", "rejected"],
)
from ecfservice.webhook import verify_webhook_signature
ok = verify_webhook_signature(request_body, request.headers["X-ECF-Signature"], wh.secret)
Salud y padrón (sin API key)
client = ECFClient() # key opcional
print(client.health().status)
print(client.dgii.rnc("130478031").razon_social)
Errores
El service responde { "detail": "..." } (FastAPI).
from ecfservice import ECFAuthError, ECFValidationError, ECFConflictError, ECFNotFoundError
401→ECFAuthError404→ECFNotFoundError409e-NCF usado →ECFConflictError422payload / rango / P12 / header faltante →ECFValidationError
Qué no hace este SDK
- No valida el XSD DGII (lo hace el service).
- No crea rangos e-NCF; solo los lista.
- El
201decreateesreceived, no el veredicto fiscal. Usa webhooks oclient.ecf.get.
Licencia
MIT
Metadata
Release files for ecfservice 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ecfservice-0.4.0.tar.gz | 14.6 kB | Without provenance | Details for ecfservice-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ecfservice-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for ecfservice-0.4.0-py3-none-any.whl |
Total release size: 30.4 kB
Release files / ecfservice-0.4.0.tar.gz
| Download URL | ecfservice-0.4.0.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb5889d4506945c6b55ebfc2b4b8a4462e658f29ec9df81e653ace7c134b005d
|
|
BLAKE2b-256 checksum How to use checksums |
c261fd24b1a26ca5f619d94bacd6436548a54116778f43bdb1e55290d9cd3856
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / ecfservice-0.4.0-py3-none-any.whl
| Download URL | ecfservice-0.4.0-py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
938db04d2e4270abcc1afc1badc7cfc75100c60d1014f76cdd47a11d4b33a759
|
|
BLAKE2b-256 checksum How to use checksums |
eb590c43646bde86bd8d62c25e07d455eef965eb7403a7cbb5216ae214717ed2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for ecfservice 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.