Activity: Evaluate API reference docs
I need your input — I'm conducting a survey about trends in developer documentation for 2020. If you write docs for developers, please take this survey. (You can view the ongoing results viewed here.)
After completing the API reference tutorial, you’re ready to start an activity that gives you more experience in creating and editing API reference documentation. In this activity, you’ll evaluating some API reference topics to identify issues.
Activity: Evaluate API reference docs for core elements
In this activity, you’ll review API reference documentation and identify the common elements. To evaluate the API reference docs:
Choose three of the following sites. In the three you choose, analyze the API reference sections (where the endpoints are listed):
- Nexmo API reference
- Twitter API reference
- Stripe API reference
- Azure API reference
- Flickr API reference
- YouTube API reference
- Splunk API reference
- Zomato API reference
- Paypal API reference
- Basecamp API reference
- OpenSecrets API reference
- Dropbox API reference
- DBS Developers API
- Adyen Docs
- NBG Technology Hub
In the reference documentation, identify each of the following sections (if they exist):
The sections might be named differently in the API doc sites you browse, but they’re usually recognizable to some degree (if included). If you’re finding it somewhat difficult to locate them, this is part of the wild west of terminology and organization when it comes to API documentation.
Assess the API reference documentation by answering the following questions for each section:
- Is the description action-oriented?
- Is it a brief 1-3 sentence summary?
Endpoints and methods:
- How are the endpoints grouped? (Are they listed all on the same page, or on different pages? Are they grouped by method, or by resource?)
- How are the methods specified for each endpoint?
- How many types of parameters are there (header, path, query string, and request body parameters) for the endpoints?
- Are the data types (string, boolean, etc.) defined for each parameter? Are required/optional values noted?
- In what format or language is the request shown (e.g. curl, specific languages, other)?
- How many parameters does the sample request include?
- Is there both a sample response and a response schema? (And is each element in the response actually described?)
- How does the doc site handle nested hierarchies in the response definitions?
Now that you understand the essential sections to cover in documenting API endpoints, let’s look at standardized approaches for describing these sections, primarily with the OpenAPI specification and Swagger. The OpenAPI standard will help make sure you cover all the necessary details in these sections, and it will present the information to users in a way that users have become accustomed to.
33/128 pages complete. Only 95 more pages to go.