RestEase VS RestSharp

If Swagger/OpenAPI is available, save yourself a lot of trouble and generate the client using OpenAPI Generator. If not, use a library like RestEase to make it significantly easier to create the client.

Use RestEase to create your own client library. Refit is a very similar and more popular library. IMO RestEase is an improvement over Refit and I prefer it, but either will solve your problems. Both are libs that have you build interfaces describing the API endpoints, then the library handles all the boilerplate code that calls HttpClient.

Not sure about RestSharp, but with RestEase this is handled by setting it on an HttpClientHandler - https://github.com/canton7/RestEase/discussions/195

Use RestEase to make a client.

I haven't tried this myself, but to take it a step further from just sharing request types you could try using RestEase.

Honorable mentions: RestEase, RESTFulSense

I use RestEase which is heavily inspired by Refit.

Take a look at RestEase: https://github.com/canton7/RestEase

RestSharp

Use RestSharp to create a client library. It requires you to write more code, but it's still a lot less boilerplate than using HttpClient directly.

Let's say we have a simple web app that uses RestSharp, a fairly well-known REST API client library for .NET.

RestSharp:

Are you consuming REST or SOAP web services? For REST APIs you can use https://restsharp.dev/.

Can you not specify the type in the execute call, and see if you can inspect the response? var response = await client.ExecuteAsync(request); I’m on mobile so formatting, but if this is the same client, I just looked at some tests that could suggest this maybe possible https://github.com/restsharp/RestSharp/blob/dev/test/RestSharp.IntegrationTests/RequestBodyTests.cs

A way to read a rest API. If I were in your shoes, I'd probably play with RestSharp: https://restsharp.dev/

On line 16, we append the endpoint that we are going to connect to. In this example, we hit the “/addresses” endpoint. On line 17, we authenticate to Lob using Basic Authentication. Our Lob API key is placed where the username would be and we leave the password empty. Flurl sets the basic-auth headers using the WithBasicAuth method. For those using RestSharp it looks like this.