Aruba Fatturazione Elettronica

Getting credentials

1. You need an active Aruba Fatturazione Elettronica subscription with the API option enabled.
2. In the web console create the API user. Aruba issues a username of the form XXXXXXXX and a password; these are not your Aruba portal login.
3. Set ARUBA_USERNAME and ARUBA_PASSWORD. The adapter signs in at /services/auth/signin and reuses the returned bearer token, refreshing it when Aruba expires it. AnythingMCP keeps the token encrypted in connector_auth_cache.

The Sistema di Interscambio is asynchronous, and that is the whole shape of this API. You hand an invoice to Aruba, Aruba hands it to the SDI, and the SDI answers minutes or hours later with a notification. aruba_fatturazione_get_invoice_status reads where a document currently stands; the states that matter are PRESA_IN_CARICO (accepted by Aruba), INVIATA (forwarded to the SDI), CONSEGNATA (delivered to the recipient), SCARTATA (rejected — a real problem), MANCATA_CONSEGNA (the recipient's channel failed, but the invoice is still legally issued) and NON_RECAPITABILE.

A SCARTATA invoice has not been issued. It has to be corrected and resent with the same number within five days. An agent reporting revenue should exclude rejected documents, not count them.

Invoices are XML (FatturaPA), base64-encoded over this API. The tools here read status and metadata; fetching a document returns the encoded XML, which is the legally binding artefact.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.

Cloud reachability: ws.fatturazioneelettronica.aruba.it is public with a valid certificate.