Document that unsupported HTTP methods return 404, not 405 (#45190)

Co-authored-by: Sharra-writes <sharra-writes@github.com>

Author: jornith

content/rest/using-the-rest-api/troubleshooting-the-rest-api.md

@@ -73,6 +73,8 @@ You should also check for typos in your URL. For example, adding a trailing slas
 
 Additionally, any path parameters must be URL encoded. For example, any slashes in the parameter value must be replaced with `%2F`. If you don't properly encode any slashes in the parameter name, the endpoint URL will be misinterpreted.
 
+You should also confirm that you are using an HTTP method that the endpoint supports. If you send a request with an HTTP method that the endpoint does not support, you will receive a `404 Not Found` response instead of `405 Method Not Allowed`. For example, sending a `DELETE` request to an endpoint that only supports `GET` will result in a `404 Not Found` response. You can refer to the reference documentation for the endpoint to confirm the supported HTTP method.
+
 ## Missing results
 
 Most endpoints that return a list of resources support pagination. For most of these endpoints, only the first 30 resources are returned by default. In order to see all of the resources, you need to paginate through the results. For more information, see [AUTOTITLE](/rest/using-the-rest-api/using-pagination-in-the-rest-api).