Hi Federico,
Thanks a lot for you response and thanks for welcoming me to the group. i appreciate your policy, I will look at the API's you have mentioned and my current need will not satisfied with the list. Let me explore the possibility of developing additional ones I need. Thanks C On Friday, March 9, 2018 at 2:52:31 PM UTC+5:30, Federico Capoano wrote: > > Hi Chetansk and welcome, > > our policy for building features is the following: > > - when a need to accomplish something arises > - and this need is in line within our core values > <http://openwisp.io/docs/general/values.html#core-values> > - and the need is strong enough that someone is willing to invest > resources in building it > - then we start evaluating it and we build it > > Therefore, only some modules of OpenWISP have APIs for the moment: > > > - the network-topoogy-module: because we needed to get the data to > feed to the javascript data visualization library and because we needed > routers to be able to send their topology data for collecting it > - django-freeradius in order to communicate with freeradius without > the limitations of SQL, using the freeradius-rml-rest > <http://networkradius.com/doc/3.0.10/raddb/mods-available/rest.html> > module > > > For building Restful APIs in OpenWISP we use django-rest-framework > <https://github.com/encode/django-rest-framework>. > > Here's the link to the APIs in the existing modules: > > - > https://github.com/netjson/django-netjsongraph/tree/master/django_netjsongraph/api > - > https://github.com/openwisp/django-freeradius/tree/master/django_freeradius/api > > You may as well develop the API you need without editing the source code > of OpenWISP. You can create a new django app, create the django rest > framework views and serializers, plug that into settings.INSTALLED_APPS and > use it. I'm pretty sure many people implemented their own custom APIs to do > what they need but probably the implementation wasn't good enough to share > it in the main project, but I'm just speculating. Some people simply edit > open source software and do not contribute to it, who knows, we don't have > metrics to measure this. > > I guess that in the future as our community grows with more contributors > we'll have good (and secure) APIs to control every important aspect of > OpenWISP. > > I hope this helps. > Federico > > > On Fri, Mar 9, 2018 at 5:37 AM <[email protected] <javascript:>> wrote: > >> Hi, >> >> I was looking out for RESTfull API for openWISP2, a quick search did not >> lead to what I as looking for. Hence the question >> >> a, Is there a RESTful api for openWISP2 ? >> b. Can someone point me to docs >> c. Is someone planning/starting this stuff ? >> >> >> Thanks >> C >> >> -- >> You received this message because you are subscribed to the Google Groups >> "OpenWISP" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
