title: Coinbase API - Transfer returns response 200 instead of 201
body: <p>I am trying to create transfer between accounts of the same user with different crypto currencies using the Coinbase API. I am using it's official library which I know wasn't exactly maintained but I tried to debug everything manyually and it seems that the request it's sending to the API server is correct according to the official documentation.</p>
  <p>Specifically, it uses GuzzleHttp\Psr7 to send to /v2/accounts/[sender-account-id]/transactions the following parameters:</p>
  <pre><code>array:4 [&quot;type&quot; =&gt; &quot;transfer&quot;, &quot;amount&quot; =&gt; &quot;1&quot;, &quot;to&quot; =&gt; &quot;[receiver-account-id]&quot;, &quot;currency&quot; =&gt; &quot;USD&quot;]
  </code></pre>
  <p>According to the documentation I should receive a response with 201 status code and with the transaction info in the body. Instead I get a 200 response with empty body and no transaction is recorded on the server.</p>
  <p>If I mess up any of the fields of the request I get a proper exception and corresponding error status code. This makes me feel like there isn't something wrong with my actual request.</p>
  <p>I've noticed someone else got the <a href="https://stackoverflow.com/questions/62401461/coinbase-api-transfer-between-accounts-not-actually-transferring-despite-200-r">same problem</a> about a year ago and got no response. I hope I'd have more luck since I really don't know where to look at next and Coinbase's support link just points to stackoverflow :)</p>
  <p>Update 2021.06.07:</p>
  <p>Just to make sure I wasn't crazy, I tried today to reproduce the same problem by sending the same request without using the official library and just writing the code for the request from scratch and the result is the same.</p>
  <p>I also tried another endpoint that is supposed to return a 201 response, the one used for sending money to an external email / wallet. This one worked like a charm, I got my 201 response with the transaction info and it was also processed on the server.</p>
  <p>This makes me feel more and more like the issue is not with me but with the API endpoint itself but with how big Coinbase actually is, this somehow doesn't feel right, there's no way they wouldn't have fixed it in one year, right?</p>