Codewars Python API Docs | dltHub
Build a Codewars-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Codewars is a coding platform that provides a minimal public API to access user information and challenge data without authentication. The REST API base URL is https://www.codewars.com/api/v1 and All public API v1 endpoints do not require authentication, though an API token can be generated in user settings for other purposes..
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 Codewars data in under 10 minutes.
What data can I load from Codewars?
Here are some of the endpoints you can load from Codewars:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| users | /api/v1/users/{user} | GET | Get user information | |
| completed_challenges | /api/v1/users/{user}/code-challenges/completed | GET | data | List challenges completed by a user |
| authored_challenges | /api/v1/users/{user}/code-challenges/authored | GET | List challenges authored by a user | |
| code_challenges | /api/v1/code-challenges/{challenge} | GET | Get information about a specific code challenge | |
| clan_members | /api/v1/clans/{name}/members | GET | data | List members of a clan |
How do I authenticate with the Codewars API?
The official Codewars public API v1 endpoints are all public and do not require authentication.
1. Get your credentials
The official Codewars public REST API v1 does not require an API key for its standard, documented endpoints. While older community resources suggested an API key could be found in account settings (https://www.codewars.com/users/edit), it is no longer officially supported or required for public data access. If your use case involves advanced or private functionality (like submitting solutions), note that such endpoints are undocumented and may not be publicly accessible via standard API keys.
2. Add them to .dlt/secrets.toml
[sources.codewars_source] # No API key is required for public Codewars API v1 endpoints. # You may leave the api_key field empty or omit it from your configuration. api_key = ""
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 Codewars 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 codewars_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline codewars_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset codewars_data The duckdb destination used duckdb:/codewars.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 users and code-challenges from the Codewars 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 codewars_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.codewars.com/api/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "Authorization", "location": "header"}, }, "resources": [ {"name": "completed_challenges", "endpoint": {"path": "api/v1/users/{user}/code-challenges/completed", "data_selector": "data"}}, {"name": "clan_members", "endpoint": {"path": "api/v1/clans/{name}/members", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="codewars_pipeline", destination="duckdb", dataset_name="codewars_data", ) load_info = pipeline.run(codewars_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("codewars_pipeline").dataset() sessions_df = data.completed_challenges.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM codewars_data.completed_challenges LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("codewars_pipeline").dataset() data.completed_challenges.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 Codewars 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 Codewars?
Request dlt skills, commands, AGENT.md files, and AI-native context.