JSON Server Python API Docs | dltHub
Build a JSON Server-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
JSON Server is a Node.js package that creates a full fake REST API from a JSON file, intended for prototyping and mocking backends for frontend development. The REST API base URL is http://localhost:3000 and Authentication is provided by the third-party json-server-auth middleware, which supports JWT-based 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 add "dlt[hub]" and start loading JSON Server data in under 10 minutes.
What data can I load from JSON Server?
Here are some of the endpoints you can load from JSON Server:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| resources | / | GET | List all resources (paginated if params provided) | |
| resource_item | // | GET | Retrieve a single resource by ID | |
| create_resource | / | POST | Create a new resource | |
| update_resource | // | PUT | Update an existing resource | |
| patch_resource | // | PATCH | Partially update a resource | |
| delete_resource | // | DELETE | Delete a resource |
How do I authenticate with the JSON Server API?
The core JSON Server does not provide native authentication. Authentication is typically added via the 'json-server-auth' middleware, which uses JWTs; the client must perform a POST request to a /login endpoint with email and password in the body to receive a token.
1. Get your credentials
Standard JSON Server instances do not provide a native dashboard or API key management system, as it is a development-only mock server. To secure your instance, you must manually implement authentication middleware (such as json-server-auth) in your project code to handle Authorization headers. If your specific environment requires a token, you must obtain it via the registration/login flow established in your custom middleware (e.g., POST requests to /login) and manually manage the credential in your dlt environment.
2. Add them to .dlt/secrets.toml
[sources.json_server_source] json_server_api_key = "your_bearer_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 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 JSON Server 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 json_server_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline json_server_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset json_server_data The duckdb destination used duckdb:/json_server.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 /posts from the JSON Server 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 json_server_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:3000", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "resources", "endpoint": {"path": "{resource}", "data_selector": "data"}}, {"name": "resource_item", "endpoint": {"path": "{resource}/{id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="json_server_pipeline", destination="duckdb", dataset_name="json_server_data", ) load_info = pipeline.run(json_server_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("json_server_pipeline").dataset() sessions_df = data.resources.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM json_server_data.resources LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("json_server_pipeline").dataset() data.resources.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 JSON Server 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 JSON Server?
Request dlt skills, commands, AGENT.md files, and AI-native context.