FortnitePy Python API Docs | dltHub
Build a FortnitePy-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
FortnitePy is an asynchronous Python library for interacting with Fortnite and Epic Games' API and XMPP services. The REST API base URL is https://fortnite-api.com and authentication is managed internally by the library using specific Auth classes (e.g., AdvancedAuth) that handle login flows..
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 add "dlt[hub]" and start loading FortnitePy data in under 10 minutes.
What data can I load from FortnitePy?
Here are some of the endpoints you can load from FortnitePy:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| item_shop | v2/shop/br | GET | data | Current item shop items |
| br_news | v2/news | GET | data | Fortnite Battle Royale news |
| cosmetics | v2/cosmetics/br | GET | data | List of cosmetics |
| player_stats | v2/stats/br/v2 | GET | data | Battle Royale player statistics |
| cosmetics_search | v2/cosmetics/br/search | GET | data | Search cosmetics by query |
How do I authenticate with the FortnitePy API?
FortnitePy is an asynchronous Python library, not a standalone REST API, used to interact with Epic Games' Fortnite API and XMPP services; it handles authentication internally via classes like AdvancedAuth which manage device authorization codes and credentials.
1. Get your credentials
To obtain credentials, initialize the client using fortnitepy.AdvancedAuth, which facilitates the generation of persistent Device Auth credentials. 1. Log in to the Epic Games account here to generate an authorization code. 2. Copy the hex-encoded authorization code from the redirected URL (expires in 5 minutes). 3. Upon the first successful launch with prompt_authorization_code=True, the library will automatically generate and store device credentials. You should implement a storage mechanism (e.g., in a JSON file) to cache these generated credentials for future sessions.
2. Add them to .dlt/secrets.toml
[sources.fortnitepy_source] auth = "REPLACE_ME"
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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 FortnitePy 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:
uv run python fortnitepy_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fortnitepy_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fortnitepy_data The duckdb destination used duckdb:/fortnitepy.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 fortnite_get_timeline and fortnite_grant_access from the FortnitePy 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 fortnitepy_source(auth=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://fortnite-api.com", "auth": {"type": "api_key", "api_key": auth, "name": "device_auth_details"}, }, "resources": [ {"name": "item_shop", "endpoint": {"path": "v2/shop/br", "data_selector": "data"}}, {"name": "br_news", "endpoint": {"path": "v2/news", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fortnitepy_pipeline", destination="duckdb", dataset_name="fortnitepy_data", ) load_info = pipeline.run(fortnitepy_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("fortnitepy_pipeline").dataset() sessions_df = data.item_shop.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fortnitepy_data.item_shop LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fortnitepy_pipeline").dataset() data.item_shop.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 FortnitePy data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for FortnitePy?
Request dlt skills, commands, AGENT.md files, and AI-native context.