faq

Q: after requesting an API Key, nothing was emailed to me - where is it?
A: assuming the Key generation on our side worked (you should have seen an error page after requesting a Key if it failed), then either your new Key email has been junked by an email filter at your end, or something broke on our server. Please get in Contact, and we'll fix you up.

Q: why do you use SSL for API calls?
A: the API Key is sent as part of the client request URL; using HTTPS ensures that it is encrypted at the client side (and thus cannot be sniffed).

Q: when are you releasing Scan Module X?
A: new Scan Modules are being built and released approximately every two weeks, and so if there's a specific Scan Module that you would like to see implemented, let it be known and get in Contact!

Q: can I build my own custom Scan Modules?
A: yes, soon! stay tuned…

Q: I've been experiencing long scan times, why is that?
A: the core Engine is awaiting the inclusion of PHP acceleration, memcached and OO implementation in parts that do not already have it

Q: I don't like XML - can I get JSON returned from the API instead?
A: it's on the roadmap - XML was chosen because that's what the developers had experience in, but JSON support will be launched at the start of Q2 2010

Q: how can I determine the individual Scan Module weightings?
A: these are not currently published because they form part of the secret source with which the overall twam score is computed