ardalis/ApiEndpoints

A project for supporting API Endpoints in ASP.NET Core web applications.

View on GitHub ↗Jump to charts ↓

ardalis/ApiEndpoints has 3k+ stars and 200+ forks on GitHub, is written in C#, and was last pushed on Mar 9, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 21st, 2026
Created on February 9th, 2020
Open Issues & Pull Requests: 20 (+0)
GitHub issues: Enabled
Number of forks: 231
Total Stargazers: 3,196 (+0)
Total Subscribers: 52 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.5 days
Mean response time: 246.1 days
90th percentile: 854.4 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 652 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • good first issue (2)
  • help wanted (2)
  • dependencies (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

API Endpoints is a library that provides an alternative architectural pattern for building API handlers in ASP.NET Core web applications.

The library addresses the common pattern of organizing API logic in ASP.NET Core by offering a way to structure endpoints as self-contained classes rather than relying solely on controller-based approaches. Each endpoint encapsulates the request handling logic, validation, and response generation in a single, focused unit. This approach promotes separation of concerns and makes it easier to locate and test individual API operations without navigating through large controller classes.

Developers should consider API Endpoints for projects where endpoint organization and maintainability are priorities, particularly in applications with many API routes where controller classes might become unwieldy. The pattern works well for teams that prefer explicit, single-responsibility classes over the traditional controller pattern. This is especially useful in larger codebases where keeping related logic together at the endpoint level reduces cognitive load compared to spreading functionality across multiple controllers.

The project maintains steady activity with regular commits addressing bug fixes and feature enhancements. Pull requests are reviewed and merged consistently, indicating active maintenance. Issues are addressed with reasonable responsiveness, and the codebase receives updates that reflect ongoing refinement of the core patterns and supporting infrastructure.