I added a section to my API documentation course on native library APIs. Check it out and let me know what you think.
By the way, I’m never quite sure what to call these kinds of APIs, but it seems that “native libraries” is better than either platform APIs, library APIs, or class-based APIs for the following reason:
“Platform APIs” gets confused with API platforms that actually have APIs for managing your content on the platform. “Library APIs” gets confused with APIs focused literally on libraries and library sciences. And “class-based APIs” is too narrowly focused on the C programming language family.
Admittedly, I have the least experience with native library API documentation, so writing out this course material is in some ways helpful to me.
At my current job, there was a lot of documentation debt when I arrived. My focus on the native library APIs has been mainly on how to deploy, configure, and call the API instead of the class reference documentation. There are a lot of classes in the API used by a small fraction of users who have yet to complain about the existing engineering-written doc, so it’s never been a huge priority to dig into.
Additionally, the lead engineer is surprisingly articulate and precise with words (despite his grumpy demeanor). Still, this doc is on my to-do list, and someday I’m going to overhaul it all.
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.