Skip to main content
WritingVideosSpeakingCodeAbout

Ecosystem

The API ecosystem

An API built with api-toolbox and a client built with sdk-toolbox speak the same standards, because both are written to the same RFCs. apiguide.dev explains each standard, Kit starts an API on them, and Flagpole shows one running.

Five parts. One set of standards.

The standards. Who explains each one, who serves it, who reads it.

All of them →

Of the 32 standards the two packages implement, 13 are on both sides of the wire, so a response api-toolbox sends is one sdk-toolbox knows how to read. The standards table has every one, with what each package does with it and the apiguide.dev page that explains it.

Why they exist. The two articles they launched with.

Oct 202617 min read
API Design

Most of Your API Has Already Been Designed

Error formats, retries, lost updates, webhook signing: the IETF has already answered them. api-toolbox brings those answers to Laravel, one RFC per feature.

Oct 202618 min read
API Design

Most of Your SDK Has Already Been Designed, Too

Retries, rate limits, pagination, lost updates: the API already tells your client what to do. sdk-toolbox makes a PHP SDK listen, one RFC at a time.