NFT Port Python API Docs | dltHub

NFTPort is a multi‑chain API that provides NFT data and metadata for Ethereum, Polygon and other supported chains. The REST API base URL is https://api.nftport.xyz/v0 and All requests require an API key passed in the Authorization 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 NFT Port data in under 10 minutes.

---

What data can I load from NFT Port?

Here are some of the endpoints you can load from NFT Port:

---

How do I authenticate with the NFT Port API?

Authentication is performed by providing your NFTPort API key in the Authorization header as Authorization: API_KEY <your_api_key>.

1. Get your credentials

1. Log in to your NFTPort account at https://dashboard.nftport.xyz.
2. Navigate to the API Keys section in the left‑hand menu.
3. Click Create New API Key (if you do not already have one).
4. Copy the generated key; it will be used as the value for the Authorization header.
5. Store the key securely – it will be referenced in the dlt secrets.toml file.

2. Add them to .dlt/secrets.toml

Copy
[sources.nft_port_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 NFT Port 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 nft_port_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline nft_port_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 nft_details and contract_nfts from the NFT Port 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 nft_port_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.nftport.xyz/v0",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "contract_nfts", "endpoint": {"path": "nfts/{contract_address}", "data_selector": "nfts"}},
            {"name": "account_nfts", "endpoint": {"path": "accounts/{account_address}", "data_selector": "nfts"}}
        ],
    }
    yield from rest_api_resources(config)


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

SQL (DuckDB example):

Copy
SELECT * FROM nft_port_data.nft_details LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("nft_port_pipeline").dataset()
data.nft_details.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 NFT Port 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

401 Unauthorized

Occurs when the Authorization header is missing, malformed, or contains an invalid API key. Verify that the header is exactly Authorization: API_KEY <your_api_key> and that the key is active.

429 Rate Limit Exceeded

The API enforces a request rate limit per API key. If you receive this response, back‑off for a few seconds and retry. Consider implementing exponential back‑off or reducing request frequency.

400 Bad Request

Returned when required path parameters are missing or when query parameters have invalid values (e.g., unsupported chain name). Check the endpoint URL and parameter values against the documentation.

Pagination Issues

Endpoints that return large collections use page_number/page_size or a continuation token. If records are missing, ensure you are passing the correct pagination token from the previous response.

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