Handling versioned api #134

Activity

1. dannyfraser commented on Jun 12, 2018

   

   dannyfraser

   on Jun 12, 2018

   Author

   More actions

   Further research shows that the default behaviour is

   If you don’t specify the version number then you will default to version 1 of the Model, Search and Util APIs and version 3 of the Action API.

   https://docs.ckan.org/en/ckan-1.6/apiv3.html
2. wardi commented on Jun 12, 2018

   

   wardi

   on Jun 12, 2018

   Contributor

   More actions

   ckanapi only uses the action api and so far there has been no update to the action api version. It's not a bad idea to add a parameter to allow a client to select the version, on the chance that we do come out with an action api v4 in the future.
3. zotya commented on May 22, 2019

   

   zotya

   on May 22, 2019

   More actions

   I had a similar issue, but my problem was, that the url for action api is not located on 'api/action/'.
   I made a fork, and implemented a configurable url for the action api:
   eea@cee14cd

   Now, when I initialize the RemoteCKAN, I can set the url for api:

   ckanapi.RemoteCKAN(self.__address,
               self.__apikey,
               self.__user_agent,
               base_url='myapilocation/action/')