Nordic APIs Python API Docs | dltHub

nRF Cloud is a cloud platform from Nordic Semiconductor that provides device management, location services, firmware updates (FOTA), and telemetry APIs for cellular IoT devices. The REST API base URL is https://api.nrfcloud.com/v1 and All user requests require a Bearer token (API key) in the Authorization header; device or C2C requests may require JWTs..

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 Nordic APIs data in under 10 minutes.

---

What data can I load from Nordic APIs?

Here are some of the endpoints you can load from Nordic APIs:

---

How do I authenticate with the Nordic APIs API?

User-facing REST endpoints use an API key supplied as a Bearer token in the Authorization header (Authorization: Bearer <api_key>). Device- or cloud-to-cloud endpoints use JWTs where indicated in the API reference.

1. Get your credentials

1. Sign in to your nRF Cloud account or team. 2) Open the team/account settings or API keys section in the nRF Cloud portal. 3) Create a new API key (token) and copy the value. 4) Use this token as a Bearer token in the Authorization header for API requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.nordic_apis_source]
api_key = "your_nrfcloud_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 Nordic APIs 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 nordic_apis_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline nordic_apis_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 all_devices and messages from the Nordic APIs 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 nordic_apis_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.nrfcloud.com/v1",
            "auth": {
                "type": "bearer",
                "token": api_key,
            },
        },
        "resources": [
            {"name": "all_devices", "endpoint": {"path": "All-Devices"}},
            {"name": "messages", "endpoint": {"path": "Messages"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="nordic_apis_pipeline",
        destination="duckdb",
        dataset_name="nordic_apis_data",
    )
    load_info = pipeline.run(nordic_apis_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("nordic_apis_pipeline").dataset()
sessions_df = data.messages.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM nordic_apis_data.messages LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("nordic_apis_pipeline").dataset()
data.messages.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 Nordic APIs 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 Unauthorized, verify you are using a valid team API key as a Bearer token in the Authorization header (Authorization: Bearer <api_key>). For device endpoints that require JWTs, ensure the token is signed and not expired.

Rate limiting and quotas

The docs do not publish public rate-limit headers on the overview; if you encounter 429 responses, implement exponential backoff and consult nRF Cloud support or your account plan for limits.

Pagination

Some listing endpoints in the API reference may paginate results. Check the OpenAPI schema for parameters like page, limit, offset or next links; if you get truncated lists, use the documented pagination parameters or follow returned next/continuation tokens.

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