Rick and Morty API Python API Docs | dltHub

Build a Rick and Morty API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Rick and Morty API is a public REST and GraphQL API exposing characters, locations, and episodes data from the Rick and Morty TV show. The REST API base URL is https://rickandmortyapi.com/api and no authentication required; public API.

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 Rick and Morty API data in under 10 minutes.


What data can I load from Rick and Morty API?

Here are some of the endpoints you can load from Rick and Morty API:

ResourceEndpointMethodData selectorDescription
characters/characterGETresultsList characters (supports pagination and filtering); single character by id at /character/{id}
locations/locationGETresultsList locations; single location by id at /location/{id}
episodes/episodeGETresultsList episodes; single episode by id at /episode/{id}
character/character/{id}GETSingle character object
episode/episode/{id}GETSingle episode object

How do I authenticate with the Rick and Morty API API?

The API is public and does not require API keys or tokens. All requests are plain HTTPS GET requests and return JSON.

1. Get your credentials

No credentials required. Use the endpoints directly over HTTPS.

2. Add them to .dlt/secrets.toml

[sources.rick_and_morty_api_source]

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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

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:

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 Rick and Morty API 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:

python rick_and_morty_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline rick_and_morty_api_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 characters and episodes from the Rick and Morty API 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 rick_and_morty_api_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://rickandmortyapi.com/api", "auth": { "type": "", "": , }, }, "resources": [ {"name": "characters", "endpoint": {"path": "character", "data_selector": "results"}}, {"name": "episodes", "endpoint": {"path": "episode", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="rick_and_morty_api_pipeline", destination="duckdb", dataset_name="rick_and_morty_api_data", ) load_info = pipeline.run(rick_and_morty_api_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("rick_and_morty_api_pipeline").dataset() sessions_df = data.characters.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM rick_and_morty_api_data.characters LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("rick_and_morty_api_pipeline").dataset() data.characters.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 Rick and Morty API data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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.


Troubleshooting

Authentication failures

The API is public and requires no authentication; authentication errors should not occur.

Pagination and rate limits

List endpoints return an "info" object with pagination fields: count, pages, next, prev. Use the "next" URL to iterate pages. Community notes indicate a rough limit of ~10,000 requests per day; implement client‑side throttling if needed.

Not found and bad requests

404 is returned for non‑existent resources (e.g., an invalid id). 400 may be returned for malformed query parameters or unsupported filters.

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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Rick and Morty API?

Request dlt skills, commands, AGENT.md files, and AI-native context.