Let’s face it, the manual process of documenting REST APIs sucks big time. The process goes like this:
- Craft a cURL request for an API Endpoint.
- Copy the response.
- Narrate the API, paste the cURL and response on an editor.
- Edit the response, describe necessary request and response headers, query parameters etc.
- Repeat steps 1-4 for each of your tens of Endpoints.
- Publish the documentation on the web.
- Repeat these steps for each release.
This is a laborious process. However, it doesn’t have to be this way. Meet SpyREST to see how it produces purely organic, automated, replayable, published, version aware and customizable API Documentation for you.
This is how it works:
- You script the API calls using any scripting you prefer, including bash/cURL, automated test frameworks, etc. For example, using a test framework:
1 2 3 4 5 6 7
- Use the SpyREST http proxy
http://SpyREST.com:9081to perform this call on a real API.
- You get the same response, and SpyREST produces a fully baked API documentation as you see here:
Try here if you want to see for yourself:
See the documentation at
Drop me a line if you’d like to use this to publish your API documentations.