arca-status
¿Están funcionando los web services de ARCA/AFIP? Averigualo desde Python o la terminal, sin certificados ni clave fiscal.
Cuando ARCA se cae, tu integración de facturación electrónica se cae con ella. arca-status consulta el método FEDummy de WSFEv1 — que devuelve la salud de los servidores de ARCA (AppServer / DbServer / AuthServer) sin necesidad de ticket WSAA ni certificado — para que sepas al instante si el problema es tuyo o de ellos.
Parte del toolkit de FactuARCA, el servicio que factura en ARCA automáticamente desde Zoho Books.
Instalación
pip install arca-status
CLI
$ arca-status
WSFEv1 [produccion]: OK app=OK db=OK auth=OK (412 ms)
$ arca-status --env homologacion --wsaa
WSFEv1 [homologacion]: OK app=OK db=OK auth=OK (388 ms)
WSAA [homologacion]: ALCANZABLE (HTTP 200, 201 ms)
$ arca-status --json
{
"wsfev1": {
"env": "produccion", "reachable": true,
"app_server": "OK", "db_server": "OK", "auth_server": "OK",
"latency_ms": 412, "error": null, "service": "wsfev1", "ok": true
}
}
El exit code es 0 si WSFEv1 está OK y 1 en caso contrario — útil en scripts y health checks.
Uso como librería
from arca_status import probe_wsfe, probe_all
s = probe_wsfe("produccion")
if not s.ok:
print(f"ARCA con problemas: app={s.app_server} db={s.db_server} auth={s.auth_server}")
# Ambos servicios (WSFEv1 + reachability de WSAA) en un dict serializable:
probe_all("produccion")
probe_wsfe() nunca levanta excepción: ante un problema de red/TLS devuelve un WsfeStatus con reachable=False y el error en .error.
Cómo funciona
FEDummy es un método público de WSFEv1 pensado justamente para monitoreo: no lleva la sección Auth (token/sign/cuit) que exigen el resto de las operaciones, así que no hace falta ni certificado ni delegación. arca-status también resuelve el detalle de que los servidores de ARCA usan claves DH cortas que el OpenSSL por defecto de Python 3.10+ rechaza (baja SECLEVEL a 1 solo para esos hosts).
| Servicio | Producción | Homologación |
|---|---|---|
WSFEv1 (FEDummy) |
servicios1.afip.gov.ar |
wswhomo.afip.gov.ar |
| WSAA (reachability) | wsaa.afip.gov.ar |
wsaahomo.afip.gov.ar |
Desarrollo
pip install -e ".[dev]"
pytest
ruff check .
Licencia
MIT © FactuARCA.
Hecho por FactuARCA — facturá en ARCA automáticamente desde Zoho Books.
Metadata
Release files for arca-status 0.1.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 |
|---|---|---|---|---|
| arca_status-0.1.0.tar.gz | 7.6 kB | With provenance | Details for arca_status-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| arca_status-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for arca_status-0.1.0-py3-none-any.whl |
Total release size: 15.6 kB
Release files / arca_status-0.1.0.tar.gz
| Download URL | arca_status-0.1.0.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
347db5d9f129ff459cd8b487778e1c8a9a76e4afbe7106f3d7abb48278e8431c
|
|
BLAKE2b-256 checksum How to use checksums |
168a9bdac8029f3e049c17d6aed75e0e549f477eea449ae7a8ef0203653b6f87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logRelease files / arca_status-0.1.0-py3-none-any.whl
| Download URL | arca_status-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
183993ab461e029222ad0a7f69057a3c445d640c56ce4e601e864f2e0e14fada
|
|
BLAKE2b-256 checksum How to use checksums |
1cebc96796493b4175e08f86ba2e8f14f525523fe95d61f76088b9ea52149b4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logSecurity for arca-status 0.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for arca_status-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logA 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.