---
title: "When should I use async and await in an ASP.NET Core API?"  
description: "When should I use async and await in an ASP.NET Core API?"  
author: "Natalia Volkova"  
published: 2026-11-13  
updated: 2026-11-13  
canonical: https://www.mindstick.com/forum/163001/when-should-i-use-async-and-await-in-an-asp-net-core-api  
category: "C# and .NET"  
tags: ["asp.net core", "async await", "performance", "c#", "web api"]  
reading_time: 1 minute  

---

# When should I use async and await in an ASP.NET Core API?

Should every controller action be async? I have heard it makes the API faster, but I also see people saying it does not help.

## Replies

### Reply by Sofia Rodriguez

Async helps when your code waits on something outside the CPU: a database query, an HTTP call, a file read. While it waits, the thread goes back to the pool and can serve another request. That lets a server handle more concurrent requests with the same number of threads. It does not make a single request finish sooner.

Use it for I/O. Do not wrap CPU-heavy work in Task.Run on the server, because you just move the work to another thread.

Common mistakes:

- Calling .Result or .Wait() on a task. This can block threads and, in some contexts, deadlock.
- Mixing: an async method that calls a blocking database call inside it gains nothing.
- Forgetting to pass the CancellationToken so work stops when the client disconnects.

In a modern ASP.NET Core API, making database and HTTP actions async is the normal default.


---

Original Source: https://www.mindstick.com/forum/163001/when-should-i-use-async-and-await-in-an-asp-net-core-api

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
