~/talk

REST API design good practices

Talkat VinnytsiaJS 2018 · on Saturday, 2018-07-21· [api-design, web-platform]
links:none on file
slides:none on file

REST APIs start from business assets: expose resources not RPC actions, keep base URLs simple and use nouns in URLs. Use standard HTTP verbs (GET/POST/PUT/PATCH/DELETE), push complex options into query parameters and support field views so responses return only requested fields. Favor a small, predictable error set (400/500) and version URLs when breaking changes arise; aim for Richardson level 2 rather than hypermedia. Tooling stack examples: OpenAPI v3, Postman, Runscope/loader.io, Apigee and note there are over 20,000 public APIs today.

AI-written summary · about

  1. 0:00Introduction
  2. 7:29REST API as product
  3. 10:07Design principles
  4. 17:56HTTP verbs usage
  5. 20:51Error handling
  6. 22:18API versioning
  7. 24:31REST maturity model
  8. 28:13Design tools
  9. 32:39API testing
  10. 36:31API management
  11. 39:05Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.