Fatture in Cloud

Getting a token

1. Register an application in the Fatture in Cloud developer console (developers.fattureincloud.it). You receive a client id and client secret.
2. Run the authorization-code flow once for the account, requesting the scopes you need — entity.clients:r, entity.suppliers:r, issued_documents:r, received_documents:r, products:r, and the :a variants for write. Keep the refresh token.
3. Set FIC_CLIENT_ID, FIC_CLIENT_SECRET, FIC_REFRESH_TOKEN and FIC_COMPANY_ID. AnythingMCP refreshes the access token on its own.

Every path carries a company id. A Fatture in Cloud account can hold several companies (aziende) and each has its own numeric id; FIC_COMPANY_ID fixes this connector to one. fatture_in_cloud_list_companies is the exception — it is the one call that works without it, and it tells you which ids exist.

Issued vs received. issued_documents are the documents you send (invoices, quotes, credit notes, delivery notes); received_documents are supplier invoices you have recorded. The type parameter narrows within each: invoice, quote, proforma, credit_note, order, receipt, delivery_note.

Fatturazione elettronica. Italian e-invoices carry an e_invoice flag and an ei_status that tracks the document through the Sistema di Interscambio: not_sent, sent, pending, accepted, rejected. A rejected invoice is a real accounting problem and worth asking about by name.

fieldset=detailed returns the line items and payment schedule; the default returns headers only. Ask for detail when you need it and not before, because documents are large.

Cloud reachability: api-v2.fattureincloud.it is public with a valid certificate.