Removebg Python API Docs | dltHub

Removebg is a REST API that removes image backgrounds and returns edited images or JSON metadata. The REST API base URL is https://api.remove.bg/v1.0 and all requests require an API key sent in the X-Api-Key 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 pip install "dlt[workspace]" and start loading Removebg data in under 10 minutes.

---

What data can I load from Removebg?

Here are some of the endpoints you can load from Removebg:

---

How do I authenticate with the Removebg API?

Authentication uses a single API key. Include the key in every request header as X-Api-Key (sometimes shown as X-API-Key or X-Api-Key).

1. Get your credentials

1. Sign up / log in at https://www.remove.bg/dashboard. 2) In the dashboard navigate to API / developer settings. 3) Copy the provided API key. 4) Use that key in the X-Api-Key header for requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.removebg_source]
api_key = "your_api_key_here"

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt 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:

Copy
dlt ai toolkit rest-api-pipeline install

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 Removebg 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:

Copy
python removebg_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline removebg_pipeline 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 images_remove and account from the Removebg API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def removebg_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.remove.bg/v1.0",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "images_remove", "endpoint": {"path": "removebg"}},
            {"name": "account", "endpoint": {"path": "account"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="removebg_pipeline",
        destination="duckdb",
        dataset_name="removebg_data",
    )
    load_info = pipeline.run(removebg_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):

Copy
import dlt

data = dlt.pipeline("removebg_pipeline").dataset()
sessions_df = data.images_remove.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM removebg_data.images_remove LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("removebg_pipeline").dataset()
data.images_remove.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 Removebg data to?

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

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

---

Troubleshooting

Authentication failures

If you receive 401 or 403 responses ensure your X-Api-Key header contains the correct API key. Header name variations seen in docs: X-Api-Key, X-API-Key; use the exact key from dashboard.

Rate limits

Remove.bg enforces rate limits (documentation states up to 500 images per minute, resolution‑dependent). Exceeding limits returns HTTP 429 with Retry-After header; use X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers to back off.

Common error responses

• 400: Bad request (e.g., invalid parameters or malformed multipart form)
• 401/403: Invalid or missing API key
• 413/415: File too large or unsupported media type
• 429: Rate limit exceeded (no credits charged)
• 500: Server error; retry with backoff

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

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

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack