开放我的SaaS API 证明是我做出的最明智的增长决策之一。
我经营着一个名为SocialBu的社交媒体管理SaaS，前一段时间，我决定开放一个公共API。最初，我只是想支持一些一直在请求这个功能的高级用户，但没想到接下来发生的事情。
当API上线并有了文档后，我开始注意到一些有趣的现象：
- 技术用户开始专门注册以获取API访问权限，包括代理机构、拥有自动化工作流程的营销人员，以及使用Zapier或n8n等工具的人。
- 这些用户转为付费计划的速度比普通用户快。
- 他们几乎不需要任何支持：只需阅读文档就能开始构建。
- 最重要的是，他们留了下来。一旦有人将你连接到他们的工作流程中，你就基本上嵌入了他们的系统。
我甚至没有大力推广这个API，只是悄悄地添加了文档并使其可访问。回想起来，我应该更早就这样做。
这也是我们专注于API优先产品开发的另一个原因。
我对其他产品通过API（甚至是Zapier/n8n集成）暴露出来的经历很感兴趣。同时，想了解在主要客户群体并非技术型或API消费者的情况下，有哪些策略可以进一步推广API？
查看原文
I run a social media management SaaS called SocialBu, and a while ago, I decided to open up a public API. Initially, I just wanted to support a few power users who kept asking for it, but I didn't expect what happened next.<p>Once the API was live and documented, I started noticing something interesting:<p>- Technical users began signing up specifically for API access. Agencies, marketers with automation workflows, and folks using tools like Zapier or n8n.
- These users converted to paid plans faster than normal users.
- They barely needed any support: they just read the docs and started building.
- Most importantly, they stuck around. Once someone connects you to their workflow, you're basically embedded in their system.<p>I didn't even promote the API much. Just quietly added docs and made it accessible. In hindsight, I should've done this way earlier.<p>Another reason to focus on API-first product development for us.<p>Interested in learning how it went for others having their product exposed through an API (or even Zapier/n8n integration). And, any strategies to promote the API further when your primary customer profile is not technical/API-consumer?