API providers aim to provide SDKs that translate their API specification into client code, but these SDKs are not enough to guarantee good developer experience. A critical analysis of an API's request sample code revealed red flags such as bad HTTP practice, security vulnerabilities, and hardcoded JSON. In contrast, a well-designed SDK provides layers of support for developers, including the API Consumer DX layer with features like failed call retries, configurable logging, and optimized error messages. The API Provider DX Layer offers features tailored for providers, while the language-idiomatic layer provides multi-language support to cater to developers' preferences. A great SDK is one that goes beyond mere translation of the API specification, handling repetition in a library and catering to both providers' and consumers' needs in their preferred language.