What does the The Rick and Morty API data include?

3 tables: characters (one row per character), episodes (one row per episode) and locations (one row per location).

Do I need an account with The Rick and Morty API?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each run replaces the table, so it never holds two copies of the same row.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

The Rick and Morty API

Entertainment

Ready to useNo account needed

Characters, locations and episodes from the animated series Rick and Morty, as a public fan database. Ingest delivers this data to a data warehouse you own as 3 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What people use it for

Browse every characterSee each character's species, status and gender in one table.
Explore the show's locationsLook up where each location sits and what dimension it is in.
Track episodesSee each episode's air date and title in order.

What you get

Table	Each row is
Characters `characters`	One character
Episodes `episodes`	One episode
Locations `locations`	One location

Good to know

Characters: Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
Episodes: Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.
Locations: Each run replaces the table with a fresh copy, so edits and removals at the source show up after the next run.

How it works

Choose The Rick and Morty API. The data is public, so there is nothing to sign in to.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

What does the The Rick and Morty API data include?: 3 tables: characters (one row per character), episodes (one row per episode) and locations (one row per location).
Do I need an account with The Rick and Morty API?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can The Rick and Morty API data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each run replaces the table, so it never holds two copies of the same row.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector rickandmortyapi, version 0.1.0, a REST source, status stable, authentication none.

Vendor documentation: https://rickandmortyapi.com/documentation

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`characters` The full catalogue of characters from the Rick and Morty API.	stable	full	replace	`id`	-
`episodes` The full catalogue of episodes from the Rick and Morty API.	stable	full	replace	`id`	-
`locations` The full catalogue of locations from the Rick and Morty API.	stable	full	replace	`id`	-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Get The Rick and Morty API data into your warehouse

Last updated 2026-10-16.