MediumExperience level: 3-5 years · 8-15 years1 min read

What is the Richardson Maturity Model, and is HATEOAS worth implementing?

Reviewed by Gurusankar M.

Asked inAmazonDeloitteMicrosoft
#hateoas#richardson maturity model#rest#hypermedia
Report issue

Short Answer

It grades REST maturity: L0 (RPC over HTTP), L1 (resources), L2 (HTTP verbs + status codes — where most 'REST' APIs sit), L3 (HATEOAS: responses include hypermedia links to next actions). HATEOAS adds discoverability but real-world adoption is low due to client complexity.

On this page

Concept Made Simple

Coffee Chat Question

“What is the Richardson Maturity Model, and is HATEOAS worth implementing?”

Remember It Faster

Mind Map Answer

L0
one endpoint, RPC-style
L1
multiple resources
L2
proper verbs + status codes (most APIs)
L3
HATEOAS — hypermedia links

Think Beyond the Expected

What If?

Why do most production APIs stop at Level 2 instead of full HATEOAS?

HATEOAS promises clients that discover actions via links, but in practice clients hard-code URLs anyway, and building/consuming hypermedia adds complexity for little payoff. Most teams get the value (resources + verbs + codes) at L2 and skip L3.

Real World

Knowing the model helps you discuss API design maturity in interviews; pragmatically, most 'RESTful' APIs are Level 2, and that's a defensible, common choice.

Interviewer's Expectation

Keywords they're listening for:

  • four levels
  • L2 = verbs+codes (most APIs)
  • L3 = HATEOAS/hypermedia
  • discoverability vs client complexity
  • pragmatic adoption

Common Mistakes

  • Claiming an API is 'fully REST' without HATEOAS (it's L2)
  • Over-engineering hypermedia clients ignore
  • Confusing the model levels

Best Practices

  • Aim for solid Level 2 by default
  • Add hypermedia only where it pays off
  • Document the contract regardless (OpenAPI)

Follow-up Questions

  1. What does a HATEOAS response look like (_links)?
  2. When is hypermedia actually valuable?
  3. Is GraphQL a different answer to discoverability?

Continue Learning with AI

Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.

Plain-language foundations

I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner.

Topic: HATEOAS (REST APIs)
Interview question: "What is the Richardson Maturity Model, and is HATEOAS worth implementing?"

Please:
1. Explain the core idea in simple, plain language, using an everyday analogy.
2. Define any technical terms you use.
3. Walk through one small, concrete example.
4. Finish with a single sentence I can easily remember.

Keep the tone friendly and assume I'm new to this topic.
Open inChatGPTGeminiClaude

Was this answer helpful?

Affiliate links

Tools for Your Developer Workspace

Equipment for a comfortable, productive setup.

As an Amazon Associate I earn from qualifying purchases.