Just a few limitations I've run into when programming against the API:
- Changes to Assets through the API do not generate history entries. These history entries are very useful for auditing the lifecycle of assets in our organization. As a workaroung I'm currently using the API to place assets into a temporary location, and then having the tech do a search through the WHD gui for all assets in that temporary location and then run a bulk action against those assets.
- Unable to assign/remove clients to assets through API - I could not find anything in the API documentation for this. Even if I did, I suspect that the lack of history entries would make this a moot point. Instead we need to go into each individual asset and remove the assigned users.
- Able to limit and paginate results of searches, but no documented mechanism for determining the total results that match criteria. If I do a search for tickets with a particular status (for instance "Awaiting Shipment") the API allows me to limit the number of results returned and paginate chunks of results, but without the ability to look up a total number through the API I'm forced to resort to direct SQL queries against the database to determine how many pages to present to the user through my automation tool.
One of the primary motivations for moving to the updated versions of WHD was to take advantage of the API instead of attempting to directly manipulate the database as my predecessor did. I'm hoping that future updates will continue to build out the API.
