npm install zaproxy
By default ZAP requires an API key to be sent with every request. This is done automatically providing you supply the same API key when you instantiate the
ZapClient that you use to run ZAP with. All following API requests will use this same API key.
You can disable the API key when running ZAP if you are on a trusted network and understand the risks. If you choose to do so, you may omit the
apiKey property of the
zapOptions object supplied to
Instantiate the Node API:
const ZapClient = ;const zapOptions =apiKey: <the key you supplied to ZAP when you started it> // I.E. 'v90dnblpqs1pcac991tn2oudl'proxy: <protocol>://<host>:<port> // I.E. '';const zaproxy = zapOptions;
Use the Node API:
For a full API list, see https://github.com/zaproxy/zaproxy/wiki/ApiGen_Index.
The Node API methods have the same signature as the API documentation, featuring both callback and promise based interfaces, making everyone happy.
The API key is no longer explicitly required on any Node API method invocations. Unless you have disabled the API key when running ZAP, simply provide it on Node API instantiation as mentioned in the Usage section and it will be provided automatically with each request to the ZAP API.
Callback mode: If you provide a callback as the last parameter, the callback will be called with error and response arguments, with the response being an object that corresponds to the JSON output of the API call.
Promise mode: If you wish to use the modern approach, simply don't provide a callback, and a native promise will be returned for you to deal with as you wish.
For help using the OWASP ZAP API refer to:
- OWASP ZAP User Group - for asking questions;
- IRC: irc.mozilla.org #websectools (eg using Mibbit) - chat with core ZAP developers (European office hours usually best)
For specific help with this Node API, contact @binarymist (the maintainer).
To report issues related to the OWASP ZAP Node API, bugs and enhancements requests, use the issue tracker of the main OWASP ZAP project.