Building an API with Apigility
summary
Apigility claims to remove the boring bits by providing an admin UI and a separate runtime engine, installed via composer, that generates working controllers and factories. It demonstrably creates a one-line ping RPC endpoint and a zero-code database-connected CRUD for an albums table, with JSON/ HAL hypermedia, pagination, validation, and structured errors via http-problem. It supports media-type or URL versioning, method negotiation, OPTIONS, and built-in OAuth2/HTTP auth; demos use curl and return correct status codes and headers.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:36Things to consider
- 3:17API Architecture
- 7:09Getting Started
- 14:54Method negotiation
- 15:27OPTIONS handling
- 15:56Error reporting (http-problem)
- 17:24Accept checking
- 19:57Versioning New version changes the namespace
- 21:45Two types Database connected API
- 41:57Validation
- 44:24Documentation
- 44:42Code-connected services
- 45:03Loan Resource class
- 45:30The data model is your code!
- 45:41Loan Resource code
- 47:12Authentication
- 47:47OAuth2 process
- 48:06Password grant type Send usemame/password & get back a token - good for trusted clients
- 48:43Request authorization code Redirect user to this URL
- 49:07Convert authorization code to token
related talks
01h 03mDeveloping and Designing RESTful Web APIs in PHP Using Apigility
34mAPI Platform: From Rest & GraphQL APIs to state-of-the-art standards in seconds
39mAPI Platform — A Daily Tool for (Un)usual Tasks
28mSay goodbye to building boring APIs with Data API builder
24mBuild The API First
35mBuilding Your API for Longevity
14mAPI in a box
35mBuilding Ambitious APIs with Ruby