2 ways to ensure your documentation doesn't fail

Auto-generate your docs based on the OpenAPI spec or use Postman

One of the most annoying things is to follow some form of documentation and none of your API calls work. As a product owner, this is not what you want your early adopters to go through.

From what I have seen most times API docs fail because the code sample or instructions are wrong or out of date.

One way to keep an up to date and accurate docs as possible is to publish the working sample you use during development.
A tool such as Postman allows you to polish up your dev API calls and publish them as API docs.

Another way is to document your APIs using the OpenAPI standard. This provides you with ready-to-use code in addition to interactive docs. I personally despise the look of the interactive docs, you might want to try Redocly instead.

Have a group for when the docs fail

This is not likely to scale over time, but it's a good thing to have this early on.
Be it Slack, Telegram, or a good old Forum, having a place where a user can seek help or ask questions could help avoid churn. A user is more likely to reach out if they have a few successes trying out your product but then hit a block.

The other good thing with having a group is that you are able to collect some useful feedback as well, such as ideas on what else needs to be documented or added to your blog.

I am currently working on contentfordevs and will be more than happy to work with anyone looking to improve their documentation or grow their blog with technical content.