Fatture in Cloud Python API Docs | dltHub

Build a Fatture in Cloud-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Fatture in Cloud is a RESTful API that provides access to the features available in the Fatture in Cloud Web interface for managing accounting and business data. The REST API base URL is https://api-v2.fattureincloud.it and All requests require an OAuth 2.0 access token passed as a Bearer token in the request header..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Fatture in Cloud data in under 10 minutes.


What data can I load from Fatture in Cloud?

Here are some of the endpoints you can load from Fatture in Cloud:

ResourceEndpointMethodData selectorDescription
clientsc/{company_id}/entities/clientsGETdataList of clients
suppliersc/{company_id}/entities/suppliersGETdataList of suppliers
productsc/{company_id}/productsGETdataList of products
issued_documentsc/{company_id}/issued_documentsGETdataList of issued documents
received_documentsc/{company_id}/received_documentsGETdataList of received documents

How do I authenticate with the Fatture in Cloud API?

Authentication is performed by passing an OAuth 2.0 access token in the Authorization HTTP header with the Bearer prefix (e.g., 'Authorization: Bearer ').

1. Get your credentials

To obtain your API credentials, follow these steps: 1. Log in to your Fatture in Cloud account. 2. Navigate to the 'Impostazioni' (Settings) menu. 3. Locate and click on the 'Sviluppatore' (Developer) section. 4. Click the 'Nuova app' (New App) button to create a new application configuration. 5. On the application management page, select your preferred authentication method (OAuth 2.0 is recommended for most integrations). 6. Once configured and saved, the dashboard will display your 'Client ID' and 'Client Secret'. Ensure you keep the Client Secret secure and never expose it in client-side code.

2. Add them to .dlt/secrets.toml

[sources.fatture_in_cloud_source] access_token = "REPLACE_ME"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Fatture in Cloud API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python fatture_in_cloud_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline fatture_in_cloud_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fatture_in_cloud_data The duckdb destination used duckdb:/fatture_in_cloud.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads https://api-v2.fattureincloud.it/oauth/authorize and https://api-v2.fattureincloud.it/oauth/token from the Fatture in Cloud API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def fatture_in_cloud_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api-v2.fattureincloud.it", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "clients", "endpoint": {"path": "c/{company_id}/entities/clients", "data_selector": "data"}}, {"name": "suppliers", "endpoint": {"path": "c/{company_id}/entities/suppliers", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fatture_in_cloud_pipeline", destination="duckdb", dataset_name="fatture_in_cloud_data", ) load_info = pipeline.run(fatture_in_cloud_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("fatture_in_cloud_pipeline").dataset() sessions_df = data.clients.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM fatture_in_cloud_data.clients LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("fatture_in_cloud_pipeline").dataset() data.clients.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Fatture in Cloud data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Fatture in Cloud?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines