RestClient.Net VS RestSharp

https://github.com/MelbourneDeveloper/RestClient.Net/blob/5263ff4cd90bdd7c4a97c600baaf2ecc7e94599c/src/RestClient.Net.UnitTests/MainUnitTests.cs#L1010

RestClient .Net is completely immutable and therefore much more thread-safe. It also works well with standard Microsoft dependency injection, and it's easy to mock. Have a look at the abstraction. If you use this, it's a one-step process for mocking HTTP calls.

https://github.com/MelbourneDeveloper/RestClient.Net/blob/e7edf5c1b40305732af3b0bd10c548996889ba97/src/RestClient.Net.Abstractions/IClient.cs#L9

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.