Suffering from API and SDK overload? Us too. We decided to wrap the APIs of all the external services we use into an old school Object-Relation-Mapping interface and it's been awesome! Documentation and onboarding fatigue is real, and if you have an API, you need to start planning for it.

Many of our clients, and we ourselves, now regularly integrate 15+ SaaS APIs and SDKs per project, even for MVPs. Each project uses different APIs. We're spending far too much time working with too many APIs and SDKs that all do things differently. This is a real problem in the field and even "standard" documentation like swagger is just not enough anymore. The talk discusses a specific potential solution, but will call for the community to start taking this issue on board collectively.