Hello!
Not much of an enhancement request, perhaps more of an FYI. I don't see much discussion around the API, so maybe this isn't the place for it. But I've seen some, so maybe it will make its way to the people who can fix it.
I've been working from the Postman Collection for the API documentation I've found a spot where the documentation appears to disagree with the API and itself. Below I've attached a screen cap of the delete asset endpoint where it shows using a query parameter to specify the asset to delete. Further down you can see in the Python example provided (the other scripts as well) that it uses a path parameter for the assetID.
The path and query parameter as shown at the top of the entry will return 404. Unless I presume, you have an asset with an assetID of 1; which should then be able complain about the query parameter. But, maybe not and when the dev team tests this locally they have an asset #1 and the DELETE goes through and that's how it's gone unnoticed.
Python example showing the path parameter:
You can see it again if you look at the exported JSON from the collection. The request url shows the query parameter and the response shows the path parameter.
And for what it's worth, Paul Miller's fork (which also shows up there) has the correct parameter for the endpoint. So, maybe this is old news and I'm just looking at the deprecated collection.
