Fatture in Cloud API Documentation
This is the complete API documentation for connecting to the Fatture in Cloud API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet Fatture in Cloud: Manage invoices, clients, products, and accounting documents. Keep reading to get started.
Quickstart
Before you run your first Fatture in Cloud request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one Fatture in Cloud connection — create or choose one in Connections. Note its
connectionId.
Every Fatture in Cloud action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/fattureInCloud/latest/actions/{actionSlug}You need a MindCloud API Key and a Fatture in Cloud connection. Then call an action such as Get Client:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/fattureInCloud/latest/actions/get-client" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Fatture in Cloud account that should run the action. MindCloud stores and refreshes the Fatture in Cloud credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
Fatture in Cloud actions
All 30 published actions for this Fatture in Cloud version. Each page documents the endpoint, arguments, and response controls.
- POSTCreate Client
- POSTCreate Issued Document
- POSTCreate Product
- POSTCreate Receipt
- POSTCreate Received Document
- POSTCreate Supplier
- DELETEDelete Client
- DELETEDelete Issued Document
- DELETEDelete Product
- DELETEDelete Received Document
- DELETEDelete Supplier
- GETGet Client
- GETGet Company Info
- GETGet Issued Document
- GETGet Product
- GETGet Receipt
- GETGet Received Document
- GETGet Supplier
- GETList Clients
- GETList Issued Documents
- GETList Products
- GETList Receipts
- GETList Received Documents
- GETList Suppliers
- GETList User Companies
- PUTModify Client
- PUTModify Issued Document
- PUTModify Product
- PUTModify Received Document
- PUTModify Supplier