title: Using transactions in ASP.NET Web API
body: <p>I have two different calls to controller in Web API. Let's say that the route for a first one is <a href="http://localhost/1" rel="nofollow">http://localhost/1</a> and for second <a href="http://localhost/2" rel="nofollow">http://localhost/2</a></p>
  
  <p>My goal is to do something like transactions. In a first call I want to send data to server. So this is where my first question comes: How can I save data for a short time on server, and not saving it into database? What's the best practice for this?</p>
  
  <p>In second call I'm sending verification code. If code is ok, than I will do something with data that client send in previous call.</p>
  
  <p>This sounds like a transaction to me. Like commit if code is ok or rollback transaction if code verification faild, but I'm not sure is it possible to use transactions in this kind of scenarios, when you have two different POST methods. </p>
  
  <p>Can someone help me with thinking about this little bit more?</p>