SDK

A collection of software development tools, libraries, and documentation that enables developers to build applications for a specific platform or framework.

An SDK, a software development kit, is the package a platform ships so developers can build against it: client libraries in each language, typed interfaces, auth helpers, CLI tools, sample code and docs, everything needed to integrate without reimplementing the protocol underneath.

Why it matters to an indie builder: the quality of an SDK predicts the cost of an integration better than the API's feature list. A good SDK handles retries, rate limits, pagination and webhook verification, the boring failure modes, so a weekend integration stays a weekend integration. When you build your own platform, shipping an SDK is what turns an API into an ecosystem.

A realistic use: wiring payments or email into a product means installing the provider's SDK, configuring a key, and calling typed methods, with the HTTP details, signing, serialization, error mapping, absorbed by the library.

Trade-offs: SDKs lag the API surface, pin you to release cycles, and hide behavior you may need to debug anyway. Compare with direct API calls when the surface is small, and see the API and webhooks blocks here for the underlying contracts.