Скачать или смотреть Resolving the request has been matched with multiple endpoints Error in ASP.NET Core

Discover how to effectively tackle the `AmbiguousMatchException` error in your ASP.NET Core API routing, and ensure your routes are properly defined.
---
This video is based on the question https://stackoverflow.com/q/77991531/ asked by the user 'kumar425' ( https://stackoverflow.com/u/20073360/ ) and on the answer https://stackoverflow.com/a/78004945/ provided by the user 'Yong Shun' ( https://stackoverflow.com/u/8017690/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: Getting routes match error even if the routes are different

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding and Resolving the request has been matched with multiple endpoints Error in ASP.NET Core

When developing web applications using ASP.NET Core, encountering routing issues can often disrupt your workflow. One common error developers face is the request has been matched with multiple endpoints. This error can be particularly frustrating, especially when it seems that you have correctly defined distinct routes. In this guide, we'll dive into the reasons for this error and how to resolve it effectively.

The Problem: Multiple Endpoints Match

This error indicates that your request has matched more than one endpoint, creating ambiguity in routing. Consider the following error details from the logs:

[[See Video to Reveal this Text or Code Snippet]]

In essence, this means that when a request is made to the root URL (/), the framework cannot determine which route to execute because two or more routes match.

Analyzing the Code

The presented controller code defines two HTTP GET methods for the CrmManagementController without overlapping paths:

[[See Video to Reveal this Text or Code Snippet]]

These methods should be reachable via api/crm-management/projects and api/crm-management/pursuits, respectively. So why the conflict? The issue lies within the routing configuration.

The Solution: Removing Conflicting Routes

In the provided Program.cs file, there is a conflicting route definition that might be causing the issue. Here’s the significant underlying code snippet:

[[See Video to Reveal this Text or Code Snippet]]

The line endpoints.MapGet("/", () => "This is the sample project"); defines a route that matches the root URL (/). When a request is made to this route, it competes against other potential matches, leading to the ambiguity noted in the error message.

Recommended Action

To resolve the error, simply remove the conflicting line from the app.UseEndpoints() configuration:

[[See Video to Reveal this Text or Code Snippet]]

By removing this line, the root URL will no longer conflict with other routes set up in the CrmManagementController. After making this change, the ambiguity should be resolved, and the application will correctly route the requests to the appropriate methods.

Conclusion

Routing is a fundamental part of ASP.NET Core applications, and sometimes minor misconfigurations can lead to significant errors like the AmbiguousMatchException. By ensuring routes are distinct and removing unnecessary or conflicting route definitions, you can maintain clean and efficient routing in your applications. If you encounter further routing issues, revisit your endpoint definitions to ensure clarity and unambiguity.

For more tips on ASP.NET Core routing and configuration, stay tuned to our blog!