Rick and Morty API
REST and GraphQL API for the Rick and Morty animated series, including all characters, locations, and episodes. Commonly used in React/GraphQL tutorials and hackathon projects.
🟢 Online · 30 ms
97.37%
10,000 req/day, no key, no credit card
No key required
Free alternatives (live ranking)
- PokéAPI — 🟢 Online · Unlimited, no key, no credit card
- JokeAPI — 🟢 Online · 120 req/min, no key, no credit card
- Random User Generator — 🟢 Online · Unlimited, no key, no credit card
Compare Rick and Morty API with…
- Rick and Morty API vs PokéAPI — Unlimited, no key, no credit card
- Rick and Morty API vs JokeAPI — 120 req/min, no key, no credit card
- Rick and Morty API vs Random User Generator — Unlimited, no key, no credit card
Frequently Asked Questions
Does Rick and Morty API require an API key?
No, Rick and Morty API is freely accessible without registration or an API key.
What is Rick and Morty API's free tier?
10,000 req/day, no key, no credit card
Is Rick and Morty API currently online?
We check Rick and Morty API every hour. The current status is shown at the top of this page. You can also see the 30-day uptime history in the chart above.
Implementation notes
When to use Rick and Morty API
The Rick and Morty API is notable for offering both REST and GraphQL access to the same dataset. It covers all 826 characters, 126 locations, and 51 episodes with pagination and filter support. Use it when you want to teach or demonstrate GraphQL alongside REST without setting up your own backend.
Common pitfalls
- The 10,000 requests/day limit is enforced per IP address and resets at midnight UTC. Automated tests or CI pipelines that hit the API without caching can exhaust the daily budget before your users do.
- Character images are hosted on a CDN within the rickandmortyapi.com domain. The `image` field returns a direct URL to a JPEG — these are not mirrored elsewhere. If the CDN is unavailable, your image rendering breaks. Download and self-host images for any production use.
- GraphQL queries are sent to `https://rickandmortyapi.com/graphql` as POST requests with a JSON body containing `query`. The REST and GraphQL APIs return identical data but different response envelope shapes — the GraphQL API wraps results under `data.characters.results` while REST uses a top-level `results` array.
- Filter parameters are case-sensitive. Searching for `status=alive` (lowercase) works; `status=Alive` returns a 404 with no results array. The docs show the correct lowercase values but it is easy to overlook.
Quick start (bash)
curl "https://rickandmortyapi.com/api/character?status=alive&species=Human&page=1"Embed this badge
Add a live status badge to your README, docs, or website.
Markdown
[](https://freeapi.watch/rick-and-morty)HTML
<a href="https://freeapi.watch/rick-and-morty"><img src="https://freeapi-builder.a10ayassine.workers.dev/badge/rick-and-morty.svg" alt="Rick and Morty API Status"/></a>