<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>curl on GoScrapy Blog</title><link>http://goscrapy.com.ar/tags/curl/</link><description>Recent content in curl on GoScrapy Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>jackgris2@gmail.com (Gabriel Pozo)</managingEditor><webMaster>jackgris2@gmail.com (Gabriel Pozo)</webMaster><lastBuildDate>Tue, 11 Apr 2023 19:23:48 -0300</lastBuildDate><atom:link href="http://goscrapy.com.ar/tags/curl/index.xml" rel="self" type="application/rss+xml"/><item><title>Documenting Api With Swag</title><link>http://goscrapy.com.ar/post/documenting-api-with-swag/</link><pubDate>Tue, 11 Apr 2023 19:23:48 -0300</pubDate><author>jackgris2@gmail.com (Gabriel Pozo)</author><guid>http://goscrapy.com.ar/post/documenting-api-with-swag/</guid><description>Think on this, you’ve finished developing a new API, and now have to write documentation to guide you when building client-side applications that consume the API. You start thinking of various ways to achieve this, and you lay out multiple alternatives like Swagger, Docusaurus, Postman and many more. You remember all the work involved in the API documentation phase and wonder if there are shortcuts to speed things up. You need to do this because who will use an API without any documentation?</description></item></channel></rss>