external-api-refit

You can consume external REST APIs by defining Refit interfaces for contracts and mapping ApiException responses to domain exceptions. This approach centralizes error handling and prevents external implementation details from leaking into your domain layer.

You add resilience to Refit HTTP clients by configuring AddStandardResilienceHandler() during dependency injection wiring. This enables retry, circuit breaker, and timeout policies automatically for your external API integration layer.

The best way to map Refit ApiException to domain exceptions is implementing a service wrapper that catches API errors and translates them. This prevents leaking external API status codes and implementation details into your internal domain logic.

This external API integration approach requires Refit for type-safe REST contracts and resilience HTTP handlers. It also relies on .NET dependency injection wiring to register the client and wrapper services properly.

Yes, you can use Refit with standard .NET dependency injection and logging. The integration layer wires clients via DI and logs external calls including start, success, and error states with HTTP status codes.

Refit API calls fail silently when error handling isn't centralized. This Skill provides logging of external calls capturing start, success, and error states with status codes, alongside mapping ApiException to domain exceptions for visibility.