Skip to content
Escriba Suite Escriba Suite

Arcanum documentation

Arcanum turns the dirty work of ARCA’s SOAP web services — building the TRA, signing it, logging in to WSAA, caching, wrapping the SOAP envelope, parsing the XML — into a clean REST call. You ask in JSON; Arcanum handles the rest.

Terminal window
curl -X POST https://your-arcanum/api/ws/padron_a5/getPersona_v2 \
  -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" \
  -d '{ "cuit": "20111111112", "params": { "idPersona": "20999999993" } }'

How it works

Section titled “How it works”

100% local WSAA signing

The TRA is signed in CMS/PKCS#7 in memory, inside your container, with node-forge — no SDK that calls a third party. The private key is stored AES-256-GCM encrypted in Postgres; the master key lives only in the environment.

Cached token, self-healing

The access ticket (Token + Sign) is cached per CUIT + service + environment, with advisory locks so two simultaneous requests never trigger two logins. A daemon renews it before it expires, and if ARCA ever rejects an expired token, Arcanum retries transparently.

Editable catalog + generic engine

Every ARCA service lives in a declarative catalog. POST /api/ws/{service}/{operation} calls any operation of any service with a JSON body. ARCA changes endpoints often — the superadmin edits them from the UI, saved and audited, with no redeploy.

Multi-client, multi-environment

Manage several CUITs from one instance, and switch between homologation and production from the interface — hot and persisted, without touching variables or redeploying.

The REST surface

Section titled “The REST surface”
  • Generic engine — POST /api/ws/{service}/{operation} reaches any catalog operation. Arcanum builds the envelope and resolves the auth for you.
  • Rich modules — the most-used services (invoicing, registry lookups, and more) also expose ergonomic REST endpoints with validation and clean JSON responses.
  • API key — every call carries X-API-Key. Arcanum is meant to sit on your own network or behind a reverse proxy with TLS.

Invoicing

Section titled “Invoicing”

The invoicing module issues and obtains the CAE with auto-numbering, handles credit and debit notes with associated vouchers, validates amounts beforehand, enforces idempotency (no double-CAE), and produces a legal PDF with ARCA’s QR. Reprints and lookups are one call away.

Certificate lifecycle

Section titled “Certificate lifecycle”

Arcanum generates the CSR; you upload it to ARCA and paste back the .crt. From then on the private key stays encrypted at rest, and the panel warns you about certificates that are about to expire.

Automate from n8n

Section titled “Automate from n8n”

Because the surface is plain REST with an API key, wiring ARCA into an n8n flow (or any system) is a single HTTP request — no SOAP, no SDK.