AnsweredAssumed Answered

Work-around for inefficient API responses?

Question asked by Matthew Gregory on Jun 1, 2016
Latest reply on Sep 16, 2016 by Eric Augustus


This is an open question for other API developers or Qualys.

I'm writing changes to the qualysapi python library.  I've recently added the Asset Group, Host List and Host Detection List API interfaces and I'm a bit annoyed by the formatting of the XML responses.  The most annoying part is that the truncation_limit (default 1k records) results in the warning element appearing at the end of the XML, right after the last Host record.  In the case of the Host List API response, the asset group id-name index appears at the end of the document as well.

 

This means that writing efficient request code is impossible.  I don't know the ID for the next request until after the entire document is downloaded.  I also have to pre-queue the asset groups before I can use the Host List responses for cross-organizational AG-based handling using iterative parsing during transmission of the document.

 

Has anyone found a work-around for this other than using tagging?  Tagging really hard to make effective in a real-time monitoring environment.

Outcomes