# dotnetcore/WebApiClient

A REST API library with better functionality, performance, and scalability than refit

Repository: https://github.com/dotnetcore/WebApiClient
Canonical: https://ross.abutalabs.com/products/webapiclient
Homepage: https://webapiclient.github.io/
Language: C#
License: MIT
License Family: permissive
Topics: webapi, retrofit, client, restful, httpclient, webclient, json, xml, form, json-rpc-client, oauth2-client, openapi, swagger, refit
Last push: 2026-07-17T00:52:43+00:00

## Health v2 (maintenance only)
Score: 82/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 92, release rhythm 60, longevity 100
- inputs: {"age_days": 3445, "days_push": 48, "days_rel": 56, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2136, forks 446 (observed 2026-08-28T04:06:17.616237+00:00)

## What it is
WebApiClient is a declarative REST API client library for .NET where developers define HTTP clients by declaring C# interfaces. It supports JSON, XML, and form serialization, AOP features like interceptors, retries, and caching, OAuth2 extensions, and OpenAPI-to-code generation, claiming 2x better performance than Refit.

## Use cases
- generate typed HTTP clients from OpenAPI/Swagger documents
- declare REST API clients as C# interfaces instead of writing HttpClient boilerplate
- call REST APIs with JSON, XML, or form serialization in .NET
- handle OAuth2 token management for API authentication
- add retries, logging, and caching to HTTP requests via interceptors
- publish trimmed/AOT .NET apps that consume web APIs

## When to choose
- you're on .NET and want a fast declarative HTTP client library
- you want to auto-generate client code from OpenAPI documents
- you need built-in OAuth2/token management extensions
- you need AOT/trimming support for your API clients

## When to avoid
- you're not on the .NET platform
- you prefer Refit's ecosystem or community size
- you need a low-level HTTP client with full manual control
- you need a server-side framework rather than a client library

## Facets
- artifact type: library
- maturity: active
- function: http-client, serialization, auth, middleware
- domain: web-development, apis, developer-tools, backend
- platform: dotnet, cross-platform
- tags: rest-client, declarative-http, refit-alternative, openapi-codegen, aot, oauth2, retrofit-style, code-generation

## Member repositories
- dotnetcore/WebApiClient (main) score 82

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:17.616237+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:51:52.507916+00:00, confidence not recorded.
  - readme: https://github.com/dotnetcore/WebApiClient (fetched 2026-08-28T04:06:17.616237+00:00, sha e37edec48fc6)
  - homepage: https://webapiclient.github.io/ (fetched 2026-08-29T10:31:48.089871+00:00, sha d8825407c8d1)
- Data as of 2026-08-30T08:39:29.467469+00:00.