Best data integration tool

Best HTTP to DuckDB data integration tool

Need the best tool to move or migrate HTTP data into DuckDB? Use ingestr for the open-source copy job, then add Bruin Cloud when the pipeline needs schedules, checks, lineage, alerts, and audit trails.

Open-source CLI Incremental loads Production ready

Short answer

Use ingestr when you need a direct, scriptable HTTP to DuckDB move.

For a HTTP to DuckDB migration, start with ingestr: an open-source CLI, a repo-friendly command, and incremental loading when the source supports it. Bruin Cloud is the upgrade when the same job needs scheduling, quality checks, lineage, alerts, and audit logs.

Start with a local CLI command and commit the workflow to your repo.

Use incremental or time-based loading when the source supports it.

Verify row counts and schema expectations before scheduling.

Add Bruin Cloud for orchestration, lineage, checks, alerts, and audit logs.

What you'll learn

How to install and set up ingestr in seconds
Connect to HTTP and DuckDB with proper authentication
Copy entire tables or specific data with a single command
Set up incremental loading for continuous data synchronization

Prerequisites

  • Python 3.8 or higher installed
  • API endpoint URL
  • Authentication credentials (if required)
  • DuckDB installed locally or database file accessible
  • Write permissions for database file location
  • Sufficient memory for in-memory operations
  • Compatible file format version

Step 1: Install ingestr

Install ingestr in seconds using pip. Choose the method that works best for you:

Recommended: Using uv (fastest)

# Install uv first if you haven't already
pip install uv

# Run ingestr using uvx
uvx ingestr

Alternative: Global installation

# Install globally using uv
uv pip install --system ingestr

# Or using standard pip
pip install ingestr

Verify installation: Run ingestr --version to confirm it's installed correctly.

Step 2: Your First Migration

Let's copy a table from HTTP to DuckDB. This example shows a complete, working command you can adapt to your needs.

Set up your connections

HTTP connection format:

http://?url=<api_url>&headers=<headers>&auth_type=<auth_type>

Parameters:

  • • url: The HTTP(S) endpoint URL
  • • headers: Custom headers as JSON (optional)
  • • auth_type: Authentication type (bearer, basic, etc.)

DuckDB connection format:

duckdb:///path/to/database.duckdb

Parameters:

  • • path: Path to database file (use :memory: for in-memory)
  • • read_only: Optional flag for read-only access
  • • threads: Number of threads to use

Run your first copy

Copy the entire users table from HTTP to DuckDB:

ingestr ingest \
    --source-uri 'http://?url=https://api.example.com/data' \
    --source-table 'public.users' \
    --dest-uri 'duckdb:///home/user/analytics.duckdb' \
    --dest-table 'raw.users'

What this does:

  • • Connects to your HTTP database
  • • Reads all data from the specified table
  • • Creates the table in DuckDB if needed
  • • Copies all rows to the destination

Command breakdown:

  • --source-uri Your source database
  • --source-table Table to copy from
  • --dest-uri Your destination
  • --dest-table Where to write data

Step 3: Verify your data

After the migration completes, verify your data was copied correctly:

Check row count in DuckDB:

-- Run this in DuckDB
SELECT COUNT(*) as row_count 
FROM raw.users;

-- Check a sample of the data
SELECT * 
FROM raw.users 
LIMIT 10;

Advanced Patterns

Once you've mastered the basics, use these patterns for production workloads.

Only copy new or updated records since the last sync. Perfect for daily updates. 

ingestr ingest \
    --source-uri 'http://?url=https://api.example.com/data' \
    --source-table 'public.orders' \
    --dest-uri 'duckdb:///home/user/analytics.duckdb' \
    --dest-table 'raw.orders' \
    --incremental-strategy merge \
    --incremental-key updated_at \
    --primary-key order_id

How it works: The merge strategy updates existing rows and inserts new ones based on the primary key. Only rows where updated_at has changed will be processed.

Common Use Cases

Ready-to-use commands for typical HTTP to DuckDB scenarios.

Daily Customer Data Sync

Keep your analytics warehouse updated with the latest customer information every night. 

# Add this to your cron job or scheduler
ingestr ingest \
    --source-uri 'http://?url=https://api.example.com/data' \
    --source-table 'public.customers' \
    --dest-uri 'duckdb:///home/user/analytics.duckdb' \
    --dest-table 'analytics.customers' \
    --incremental-strategy merge \
    --incremental-key updated_at \
    --primary-key customer_id

Historical Data Migration

One-time migration of all historical records to your data warehouse. 

# One-time full table copy
ingestr ingest \
    --source-uri 'http://?url=https://api.example.com/data' \
    --source-table 'public.transactions' \
    --dest-uri 'duckdb:///home/user/analytics.duckdb' \
    --dest-table 'warehouse.transactions_historical'

Development Environment Sync

Copy production data to your development DuckDB instance (with sensitive data excluded). 

# Copy sample data to development
ingestr ingest \
    --source-uri 'http://?url=https://api.example.com/data' \
    --source-table 'public.products' \
    --dest-uri 'duckdb:///home/user/analytics.duckdb' \
    --dest-table 'dev.products' \
    --limit 1000  # Only copy 1000 rows for testing

Choosing a HTTP to DuckDB data integration tool

If you're comparing the best data integration tools to move or migrate HTTP data into DuckDB, ask a practical question: can the first copy run locally and stay reviewable when it becomes a production pipeline?

What is the best data integration tool to move data from HTTP to DuckDB?

For most teams, ingestr is the best starting point for moving or migrating HTTP data into DuckDB. It runs as an open-source CLI from your terminal, CI, or scheduler. Use Bruin Cloud when the same pipeline needs orchestration, lineage, monitoring, checks, and governance.

Can this run as an incremental pipeline?

Yes. Use snapshot-plus-incremental or time-based extraction when the source supports it. That keeps the first load simple while making later runs smaller and easier to monitor.

When should I use Bruin Cloud with ingestr?

Use Bruin Cloud when the HTTP to DuckDB pipeline needs schedules, alerts, data quality checks, audit trails, or catalog and lineage visibility for the rest of the team.

Troubleshooting Guide

Solutions to common issues when migrating from HTTP to DuckDB.

Connection refused or timeout errors

Check your connection details:

  • Ensure database file path is accessible
  • Check file permissions for read/write access
  • Verify DuckDB version compatibility
  • Consider memory limits for large operations
Authentication failures

Common authentication issues:

  • Ensure database file path is accessible
  • Check file permissions for read/write access
  • Verify DuckDB version compatibility
  • Consider memory limits for large operations
Schema or data type mismatches

Handling data type differences:

  • ingestr automatically handles most type conversions
  • DuckDB: LIST and STRUCT types for complex data
  • DuckDB: Native support for nested data structures
  • DuckDB: Automatic type inference from files
  • DuckDB: Efficient NULL handling
Performance issues with large tables

Optimize large data transfers:

  • Use incremental loading to process data in chunks
  • Run migrations during off-peak hours
  • Split very large tables by date ranges using interval parameters

Ready to scale your data pipeline?

You've learned how to migrate data from HTTP to DuckDB with ingestr. For production workloads with monitoring, scheduling, and data quality checks, explore Bruin Cloud.

Star ingestr on GitHub