Practice API SDK vocabulary: wrapping REST APIs in SDKs, language-specific SDKs, idiomatic SDK design, auto-generated SDKs from OpenAPI specs, and multi-language SDK maintenance.
0 / 5 completed
1 / 5
What does it mean to 'wrap the REST API in an SDK'?
An SDK wraps the REST API: developers call sdk.payments.create({amount: 100}) instead of manually crafting HTTP POST requests with auth headers and JSON bodies. The SDK handles the transport layer, letting developers focus on business logic.
2 / 5
What is an 'idiomatic SDK'?
An idiomatic SDK feels native to the language: Python SDKs use list comprehensions and context managers, JavaScript SDKs use Promises and modern syntax, Go SDKs follow Go error handling conventions. Non-idiomatic SDKs feel foreign and are harder to adopt.
3 / 5
A team says 'the SDK is auto-generated from the OpenAPI spec.' What does this mean?
OpenAPI-based SDK generation uses tools (like OpenAPI Generator or Speakeasy) to produce client libraries in multiple languages from the API spec. This ensures the SDK stays in sync with the API and dramatically reduces manual SDK development effort.
4 / 5
A company announces 'we maintain SDKs for Python, JavaScript, and Go.' What ongoing commitment does this represent?
Maintaining SDKs across multiple languages is a significant ongoing investment. Each language has its own package manager, versioning norms, testing frameworks, and breaking change policies. SDK teams must track language ecosystem updates as well as API changes.
5 / 5
What is the primary advantage of language-specific SDKs over requiring developers to use the raw REST API?
SDKs dramatically reduce the integration surface: developers get type-safe methods, automatic auth headers, built-in retry logic, and idiomatic error handling. This reduces TTFSC, lowers the chance of integration bugs, and decreases support ticket volume for the API provider.