Updating resources that don't exist gives 400 error not 404 as the doc seems to suggest

Feedback
1

e.g:
After deleting the organization with ID 356 and using PUT:

curl --request PUT \
  --url "https://ppcsamurai.pipedrive.com/v1/organizations/356?api_token=$API_TOKEN" \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data 
  '{"name":"shaun.bond@ppcsamurai.com",
  "01bfbd959bbc67576cf8f5a18da0bf86ece47865":"shaun.bond@ppcsamurai.com",
   "04dd3f89ba5c390579b50a087f4a050a4db97502":"ADMIN",
  "182dfcb8d8baa886a2ff37abf4cbca78383fbc61":null,
  "340ad563612175f54f529a680477f5f6baa05ebe":2621,
  "f632840b95a9efe5747c3ff95d88fa59226a979e":6}'

Result:

 HTTP/1.1 400 Bad Request
< Content-Type: application/json
< x-correlation-id: 45b8af55-bc82-4e4f-9197-60c674bf955e
< badi: Routing: us-east-1=>us-east-1; Version: fb12; Host: b86a;
< Cache-Control: no-cache
< Access-Control-Expose-Headers: X-RateLimit-Remaining, X-RateLimit-Limit, X-RateLimit-Reset
< x-daily-requests-left: 9996
< x-frame-options: SAMEORIGIN
< Access-Control-Allow-Origin: *
< x-content-type-options: nosniff
< X-RateLimit-Limit: 20
< X-RateLimit-Remaining: 19
< X-RateLimit-Reset: 2
< Server: no-name-at-all
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Date: Mon, 21 Oct 2019 04:12:32 GMT
< Connection: close
< Strict-Transport-Security: max-age=31536000 ; includeSubDomains
{
  "success": false,
  "error": "Bad request",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API.",
  "data": null,
  "additional_data": null
}

The documentation seems to suggest that this case should return a 404