You are using an outdated browser. Please upgrade your browser to improve your experience. On one hand you’re just grabbing stuff from a data source and shoving it out as Build apis you won t hate pdf, but surviving changes in business logic, database schema updates, new features or deprecated endpoints, etc gets super difficult.
I found most resources out there to be horribly lacking or specifically aimed at one single framework. 1 are the only endpoints you’ll ever need. I’ve spent the last year working at a company called Kapture where my primary function has been to inherit, rebuild, maintain and further develop a fairly large API with many different endpoints exposing a lot of different use-cases.
The API in question was v2 when I joined the company and written in FuelPHP, utilizing a now deprecated ORM which had been hacked to death by the original developer. Routing, Database Migrations, Schema, Seeding, etc. By passing on some best practices and general good advice you can hit the ground running if you are new to API development. I either fell into, or nearly fell into, or saw others fall into.
This book will discuss the theory of designing and building APIs in any language or framework with this theory applied in examples built in PHP. I’m going to try and avoid making it code-heavy to stop you falling asleep and to keep the non-PHP developers happy.