Ask HN: Do you write a lot of SDKs for your APIs?

1 points by aprao 3 years ago | 2 comments

At work, I find myself writing a Python/Go/JS SDK for every single internal API that I implement. This might even be more prevalent for public facing APIs since creating/maintaining public API SDKs for popular languages are table stakes for usage.

- Has this generally been true in your experience as well?

- If so, are there any hacks to create these SDKs with support for best practices like pagination, retry, etc + update them them when the API changes?

ndimares 3 years ago |

There is a lot of activity in the space of SDK generators. If you have an OpenAPI schema, you should be able to find tooling that can get you 80% of the way there. Here's a small app our team put together a couple weeks ago that you might like: https://easysdk.xyz/

We've expanded support for Python and Go since we made this. If you're interested in testing out the multi-language version, let me know!

Some other solutions: -OpenAPI: http://github.com/openapitools/openapi-generator -(language specific) Go SDK: https://github.com/deepmap/oapi-codegen

Best of luck with finding a solution that works for your use case!

wing328hk 3 years ago |

One way is to auto-generate SDKs using OpenAPI Generator (http://github.com/openapitools/openapi-generator) given an OpenAPI spec.