As for the actual process of building the contract, what works well for me is using API Blueprint-style Markdown in a compatible tool like Apiary, which renders your content into Swagger-like documentation as you type. This way, I and others can mutually "live-scribe" the API contract as we discuss, and seeing it on-screen helps to get people on the same page (and sometimes highlight potential issues that would... Source: 12 months ago

I’m not sure a JS library qualifies as a PL. Or automation software (SoftStack). Or an API description language. Or a build system. Source: over 1 year ago

Create a Proper API Documentation The following open-source projects can help you with creating documentation for your APIs: APIBluePrint Swagger. - Source: dev.to / over 1 year ago

A common complaint about OpenAPI is that it’s difficult to learn and to read. Consequently, over the years we’ve seen many alternatives to OpenAPI, such as RAML, WADL, API Blueprint, and others. The problem with many of these alternatives is that in most cases they aren’t really more readable or easier to learn. Simpler description languages also tend to support less capabilities for documenting API features.... - Source: dev.to / almost 2 years ago

For the context of this post, only the first task is essential. In it, the team works together to define the API contract. They discuss data format, whether the API will be Rest or RPC, authentication, data compression, and other vital issues. The delivery of this task is the documentation, preferably in a standard like OpenAPI or API Blueprint (my preferred format). - Source: dev.to / almost 2 years ago

From this point on, I will assume, you have a basic understanding of Retrofit. To get the most out of this tutorial I would actually suggest you have a retrofit client already implemented in your application. - Source: dev.to / 4 months ago

Now you might think that in order to make the request we are going to use Retrofit but in reality we are going to be sending out an implicit intent like so:. - Source: dev.to / 11 months ago

This particular blog post will be us building on the information from the previous blog post and using the authorization code from the GitHub OAuth API in combination with Retrofit. To finally get a access token, which allows us to make requests to the API on a behalf of a user. - Source: dev.to / 11 months ago

Hey HN! If you're a fan of Swift you may have noticed that with WWDC 2023 came the (beta) release of macros. They're super powerful and expressive! I've been wishing Swift had a [Retrofit](https://square.github.io/retrofit/) style API definition library for years, and with macros it seemed like this was now possible. I'd like to show you all Papyrus, a library that turns your APIs into type-safe Swift protocols.... - Source: Hacker News / 11 months ago

When it comes to consuming APIs I can definitely recommend Retrofit. Hopefully that's enough to get you started on where to look! Source: 12 months ago