Electric Imp Python API Docs | dltHub

Build a Electric Imp-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The Electric Imp API documentation provides access to the imp class for IoT platform functionalities. The main reference is at https://developer.electricimp.com/api. The imp.setpoweren() function is part of this API. The REST API base URL is https://api.electricimp.com/v5 and All requests require a Bearer token for authentication.

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 Electric Imp data in under 10 minutes.


What data can I load from Electric Imp?

Here are some of the endpoints you can load from Electric Imp:

ResourceEndpointMethodData selectorDescription
products/productsGETdataList products (JSON:API data array)
devices/devicesGETdataList devices owned by the account
device_groups/devicegroupsGETdataList device groups
webhooks/webhooksGETdataList webhooks
logstreams/logstreamsGETdataList logstreams
accounts_login_keys/accounts/me/login_keysGETdataList login keys for the account
auth_token/auth/tokenPOSTExchange refresh token or login key for an access token
imp_setpoweren/imp/setpowerenPOSTImp power‑control endpoint (non‑GET)

How do I authenticate with the Electric Imp API?

Clients obtain an access token by POSTing credentials to /auth and include it in the Authorization: Bearer <access_token> header on all subsequent requests.

1. Get your credentials

  1. Sign in to the impCentral web app with your account. 2) Use the API endpoint POST https://api.electricimp.com/v5/auth with a JSON body containing your email/username and password to receive an access_token and refresh_token. 3) (Optional) Create a login key via POST /accounts/me/login_keys (requires Authorization and X-Electricimp-Password header) and exchange that key via POST /auth/token to obtain tokens. 4) Refresh an expired access token by POSTing the refresh_token to /auth/token.

2. Add them to .dlt/secrets.toml

[sources.electric_imp_source] access_token = "your_access_token_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:

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

1. Install the dlt AI Workbench:

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:

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 Electric Imp 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:

python electric_imp_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline electric_imp_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 products and devices from the Electric Imp 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 electric_imp_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.electricimp.com/v5", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "products", "endpoint": {"path": "products", "data_selector": "data"}}, {"name": "devices", "endpoint": {"path": "devices", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="electric_imp_pipeline", destination="duckdb", dataset_name="electric_imp_data", ) load_info = pipeline.run(electric_imp_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("electric_imp_pipeline").dataset() sessions_df = data.devices.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM electric_imp_data.devices LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("electric_imp_pipeline").dataset() data.devices.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 Electric Imp 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 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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Electric Imp?

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