CAP VS Flurl.Http

You might want to implement the outbox pattern. There’s a decent library that’ll help and is really easy to integrate. In particular, I’d look at using the transaction functionality

This might be of interest https://cap.dotnetcore.xyz/

There are many libraries in .NET that helps you implementing the outbox pattern like: MassTransit, NServiceBus, CAP. Talking about idempotency, a special mention to a specific lib from a big friend that runs on top of CAP which is called Ziggurat.

CAP is your friend https://github.com/dotnetcore/CAP

Correct but I would actually consider CAP instead. The primary reason is that CAP implements the outbox pattern out-of-box where you would need to implement this yourself with Hangfire.

Flurl and others

Is Flurl.HTTP the same as https://flurl.dev/ I assume? (It doesn't mention a specific http package)

As far as your code goes, take a look at flurl (https://flurl.dev/). It is oh so much cleaner and more readable than the httpclient stuff.

I would also add flurl to that list https://flurl.dev/. It's an amazing library and can be super helpful for quick one off API calls.

Linqpad for me, it's my go to scratch pad when testing out either new tech or edge cases and POCs than firing up a new console project. Especially when wanting to try out new nuget packages and see how they work. Even for messing with external apis I use it with Flurl, especially for apis that don't have any proper documentation.

If you working with api use flurl You can also read source code on github.

Flurl: