Skip to main content
PProfileMatch
Read Play
← Path

REST API Development · REST API Errors, Idempotency, Headers and OpenAPI Documentation

0 XP
  1. 1 current stop: learning
  2. 2 upcoming
  3. 3 upcoming
  4. 4 upcoming
  5. 5 upcoming

Finish after stop 5

Stop 1 of 5 · Help desk with a standard form

Trick to keep in mind+3 XP

Media type recipe: application/ + what it is + "+json" to say how to parse it.

RFC 9457 defines one shared shape for API errors, with members like type, title, status and detail, so a client needs a single parser. Its media type follows the common naming pattern, as in application/vnd.market.v2+json: a name for the kind of content, then a +json suffix saying the payload is JSON. Here the kind of content is a problem report.

Read it once, then a question tests whether the trick stuck.