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 / 12 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: about 1 year ago

The open-source examples are mockoon, mock-server.com, etc. Source: about 1 year ago

I've just found out MockServer and it looks awesome 🤩 so I wanted to check it out repeating the steps of my previous demo WireMock Testing which (as you can expect) uses WireMock, another fantastic tool to mock APIs. - Source: dev.to / about 2 years ago

I tend to use MockServer. With MockServer you can define inputs, so you can say that the request should look like this with that URL, etc etc. That way you can verify that the request looks okay. Source: over 2 years ago