Completed
An API is a contract
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Give it a REST - Tips for Designing and Consuming Public APIs
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Is that really REST?
- 3 Anatomy of a REST request
- 4 Anatomy of a REST response
- 5 API design - where do you start?
- 6 An API is a contract
- 7 Versioning an API
- 8 Extending an API
- 9 How do we introduce breaking changes?
- 10 Elegant deprecation
- 11 BFF - for compatibility and tailoring
- 12 Using links to construct a user interface
- 13 Hypermedia UI (consumer/publisher)
- 14 Caching - 304 Not Modified
- 15 Last-Modified header (producer)
- 16 Rate limiting - 429 Too Many Requests
- 17 Async and REST
- 18 Mini PUT/POST.../status example
- 19 Updating FileRequest status
- 20 Over consuming (consumer)
- 21 Enumerated values (consumer)
- 22 Be specific (consumer)
- 23 Resources
