Course contentsShow
← Web Development
Lesson 1480 of 2,98227. REST API Design for FrontendFree lesson

REST Maturity Levels (Richardson Model)

The four levels of REST API maturity from basic HTTP to full hypermedia-driven APIs.

REST Maturity Levels (Richardson Model)

What you'll learn: How REST APIs can be classified into four levels of sophistication, from basic HTTP to truly RESTful hypermedia-driven designs.


The Four Levels of REST Maturity

Leonard Richardson created a model to measure how "RESTful" an API truly is. Think of it like a staircase: each level builds on the previous one, adding more REST principles.

Level 0: The Swamp of POX (Plain Old XML)
Everything goes through a single URI endpoint (like /api), usually using only POST. The HTTP protocol is just a transport tunnel—no use of HTTP methods, status codes, or resource thinking. You're basically doing RPC over HTTP.

Level 1: Resources
Individual resources get their own URIs (/api/users/123, /api/products/456). You've introduced resource identifiers, but still might use only POST for everything. This is where you start thinking in resources rather than operations.

Level 2: HTTP Verbs
Now you're using HTTP methods properly: GET to retrieve, POST to create, PUT/PATCH to update, DELETE to remove. HTTP status codes (200, 404, 500) communicate results. This is where most modern APIs live—practical and functional, following the uniform interface and self-descriptive messages principles.

Level 3: Hypermedia Controls (HATEOAS)
The API response includes links to related actions and resources. Clients navigate the API by following links, not hardcoding URLs. This is true REST, achieving the HATEOAS constraint we covered earlier. Few APIs reach this level due to added complexity.

Practical Perspective

Most production APIs operate at Level 2—it's pragmatic and developer-friendly. Level 3 offers maximum flexibility but requires more sophisticated clients. There's no "wrong" level; choose based on your needs.

Key Takeaway: The Richardson Maturity Model classifies REST APIs into four levels, from basic HTTP tunneling (Level 0) to full hypermedia-driven design (Level 3), helping you understand and communicate how RESTful your API truly is.