Rick and Morty API

Beginner's Pick Games & Comics / No Auth Required Beginner HTTPS CORS
Free to Use
91 A+
Measured Score 0 50 100 Speed 28/30 Consistency 20/20 Security 20/20 Browser access 15/15 Transparency 8/15 TESTED 2026-08-10

Overview

The Rick and Morty API is a free, no-auth REST API that provides complete data about all characters, locations, and episodes from the show. You can browse all characters with their status, species, and images, or filter results by name and origin. It uses cursor-based pagination, so responses include a next URL for easy page traversal.

Beginner Tip

No API key is needed — just make a GET request directly. Use the filter parameter to search characters by name, e.g., ?name=rick to get all Rick characters.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://rickandmortyapi.com/api/character?name=rick&status=alive
Result
HTTP 200 · application/json · 11,577 bytes · compressed
Response time
37 ms (median of 3)
Transport
TLSv1.3 · TLS_AES_256_GCM_SHA384 · certificate issued by Google Trust Services
Browser CORS
Allowed — Access-Control-Allow-Origin: *
Served by
cloudflare
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
id integer 1
name string Rick Sanchez
status string Alive
species string Human
type string
gender string Male
origin object {1 fields}
location object {1 fields}
image string (url) https://rickandmortyapi.com/api/character/ava…
episode array [1 item]
url string (url) https://rickandmortyapi.com/api/character/1
created string (date) 2017-11-04T18:48:46.250Z

Captured Response

Captured from a real request to https://rickandmortyapi.com/api/character?name=rick&status=alive on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
{
  "info": {
    "count": 29,
    "pages": 2,
    "next": "https://rickandmortyapi.com/api/character?page=2&name=rick&status=alive",
    "prev": null
  },
  "results": [
    {
      "id": 1,
      "name": "Rick Sanchez",
      "status": "Alive",
      "species": "Human",
      "type": "",
      "gender": "Male",
      "origin": {
        "…": "(2 more fields)"
      },
      "location": {
        "…": "(2 more fields)"
      },
      "image": "https://rickandmortyapi.com/api/character/avatar/1.jpeg",
      "episode": [
        "https://rickandmortyapi.com/api/episode/1"
      ],
      "url": "https://rickandmortyapi.com/api/character/1",
      "created": "2017-11-04T18:48:46.250Z"
    }
  ]
}

Field Reference

id Unique identifier for the character
name Full name of the character
status Alive, Dead, or unknown
species The species of the character (e.g., Human, Alien)
image URL pointing to the character portrait image
origin Object with name and url of the character original location

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://rickandmortyapi.com/api/character?name=rick&status=alive";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 500 Requesting a path that does not exist application/json
{
  "error": "Hey! you must provide an id"
}
HTTP 404 Sending an invalid value for "name" application/json
{
  "error": "There is nothing here"
}

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

404 Not Found Requested character, episode, or location ID does not exist
Check the total count in the info object to know the valid ID range
Empty results with filter Filter value does not match any records
Try a partial name or check spelling; the name filter is case-insensitive but must match partial text
CORS error in browser Fetching from a restricted origin configuration
The API supports CORS; ensure you are using fetch() or axios correctly without the credentials mode flag

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 28/30
Consistency 20/20
Security 20/20
Browser access 15/15
Transparency 8/15
Endpoint Response Time 37ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS YES
Category Games & Comics
Difficulty Beginner
Endpoint last called: 2026-08-10

Similar APIs

View All →