Good question Prasanna, it would be tricky and not every intuitive to expose objects over REST. Instead the idea is to expose functionality.
For example you want to find our the response code for the Proxy log ID 32 over REST then that is something you can add easily even in the current version of IronWASP.
There will be a file named ApiScript.py in that file you need to add the following lines:
def get_res_code(req, res):
sess = Session.FromLog(int(req.Query.Get("log_id")), req.Query.Get("log_type"))
res.BodyString = str(sess.Response.Code)
ApiCallHandler.AddHandler("/py/get_response_code", get_res_code)
After adding it if you restart IronWASP and visit
http://localhost:8081/ironwasp/api/ then you must see '/ironwasp/api/custom/py/get_response_code' as one of the recognized REST APIs. Please note I am using 8081 in the URL since it is the default port on which IronWASP listens, if you have started it in a different URL then you need to enter that port number instead.
then the response will contain the response code in its body.
This way you can add your own REST API to IronWASP based on your requirement.
I added this as an experimental feature so never documented it. But lately these has been quite a few requests for REST support so I am considering adding built-in REST APIs for common actions like the one requested by Hiroshi and for the others provide documentation so that people can add their own extension to the API.
What do you think? :)