Help us improve

Finish the REST API

Please release the REST API into production. I have been waiting since it was first announced which seems like a very very long time ago.
  • Paul Jansen
  • Jan 10 2017
  • Started
  • Oct 10, 2018

    Admin Response

    Hi Paul, This is currently being built out on a gradual basis and is roughly 50% complete. We will be releasing all future functionality on the REST API so you will see constant improvement but this is not something that we will be delivering completely at any point in the near future i'm afraid.
  • Attach files
  • Tim commented
    13 Jul, 2019 09:49am

    This really is pathetic. We are now having to migrate from Kashflow as its API is limited and the stance in relation to refusing to work with Zapier is just really weird and anti-customer.

  • Paul Jansen commented
    18 Dec, 2018 05:20pm

    4 years on and still there is nothing of the REST API that we can use in production? 

    Generally REST APIs have versions that don't get changed with new stuff and changes made to the next version.  is  https://api.kashflow.com/v2/swagger/ui/index#! a stable v2?  or is it still "constantly changing"

     

    i am confused that the development has been stuck at 50% for several years?

     

    Please can we have a comprehensive update on the status and expectations

  • Christina Spencer commented
    12 Oct, 2018 08:33am

    Julie - there's seems to have been a small update to https://www.kashflow.com/developers/rest-api/sessiontoken/ since I last read it - the "alternative approach"  - is there an option for users to get an "External Token" so authentication can be done securely? 

    Paul: it looks like the link Julie provided is potentially useful - did you look? Though usefulness depends on better authentication still... not yet convinced of that

    Christina

  • Julie Shepherd commented
    10 Oct, 2018 03:36pm

    Hi Paul, apologies for the lack of updates, the REST API is not finished at the moment but what has been done can be accessed from:

     https://api.kashflow.com/v2/swagger/ui/index#!


  • Paul Jansen commented
    10 Oct, 2018 05:16am

    Is it safe to assume that this is never going to be finished?

  • Oliver commented
    1 Jun, 2018 08:58am

    ... time to try and bump this again I guess!

  • Paul Jansen commented
    9 Nov, 2017 04:07pm

    Are there any further updates on this? 

    I see the subscription is going up again in December 2017.  In my opinion the progress of bug fixes and new developments has been woefully slow over the last 2 years - well really since IRIS bought KashFlow.  

    To be honest, if it wasn't for the GoCardless integration I would have jumped ship already despite having been a customer since 2009.  The lack of progress with the rest API is typical of the general lack of progress from my perspective.  KashFlow seems to no longer be a leader in the sector which is really sad.

    I do hope the extra revenue from the price increase really does go to speed up development. 

  • Christina Spencer commented
    6 Feb, 2017 01:41pm

    Oh what a cunning plan... change the Canvass host and all existing items are now magically new! 

    I have been asking about the API since early 2014 ... here's an email form November 2014

    ----------------------

    Hi - am needing to do some work on my integration, and integration for a subscription site. I asked some months ago about the rest-api - but see that the pages  are still covered in warnings about use in production. Can I confirm that this is primarily because the security has not yet been dealt with?

     
    Authentication using username / password does not make sense when HTTPS and APItokens exist and are reliable - and additionally gives us some concern about your password storage methods: the suggestion that the system use character positions in the users memorable implies storage of the memorable word in plain text.  I assume that this is just because its not yet been dealt with?  As you are an accounting service I do find it strange that this lags behind!
     
    Could someone let me know when the security will be done so people could start using it?
     
    -------------------
     
    The idea of an accounts service having an API that involves plain text passwords and characters form a memorable word is frankly ridiculous. 
     
    And now, in January 2017 you repeat the "still 50% done"  
     
    Like Paul I wonder if there is any point to this conversation.
     
    Christina 
     
  • Oliver commented
    26 Jan, 2017 01:38am

    Hi,

    Is there any chance you will be developing the RESTful API soon? Or have you just totally given up on this project?

    It seems strange that you are still using a SOAP API with seemingly no active plans/development on the better, more up to date RESTful API.

    The subscription has gone up but the development seems to have stopped.....

  • Paul Jansen commented
    10 Jan, 2017 09:18am

    Is it not possible for us to start using what has been completed? it may be that all we currently require is already done.

  • Paul Jansen commented
    10 Jan, 2017 09:18am

    If you were to put what is completed into production, you could solicit from users the functions that are the priority for them which would enable you to deliver the remaining functionality most effectively.

  • KashFlow Product Manager commented
    10 Jan, 2017 09:18am

    Hi Paul,

    Unfortunately we will not be allowing access to an incomplete API. We are going to continue to build this out and will then release functionality at a later date. We have considered a partial release of functionality but we do feel that this would be a risk.

    Can I ask what it is that you are looking to do using the REST API and we can see if we can help?

    Thanks,

    Tom

  • Paul Jansen commented
    10 Jan, 2017 09:18am

    The application I need to integrate with does not support SOAP but has good support for REST.

    At this stage I need to be able to create customers and invoices and get back the relevant ID in order to retrieve the relevant data at a later date.

    To get these capabilities would have a huge positive impact.

    Thanks

  • KashFlow Product Manager commented
    10 Jan, 2017 09:18am

    Hi Paul,

    All of our REST API documentation is available via the website at http://www.kashflow.com/developers/rest-api/

    You are welcome to do any work that you need from here, however we are making constant changes to the REST API so I must warn you that any integration you do set up could be put at risk if any work is done.

    Have you taken a look at this documentation already?

    Thanks,

    Tom

  • Paul Jansen commented
    10 Jan, 2017 09:18am

    I have looked.

    You say 'constant changes' How recently were the last changes to Invoices and Customers

    Is there anywhere that changes are notified? Is there a change log?

  • KashFlow Product Manager commented
    10 Jan, 2017 09:18am

    Hi Paul,

    We do not have a public change log unfortunately. We do not publicise the availability of the REST API and as such do not provide such a log.

    The documentation will allow you to work on the REST API but there are risks involved.

    Thanks,

    Tom

  • Paul Jansen commented
    10 Jan, 2017 09:18am

    So the only way I will find out about a relevant change is when something breaks?

    Are the documentation pages updated when changes are made? could I track changes to these to get an indication of api changes?

    Can you tell me when the last changes to invoice and customer creation were?

  • KashFlow Product Manager commented
    10 Jan, 2017 09:18am

    Hi Paul,

    You can manually track the changes if you wish via the API page but again as this is not a public API we do not keep an updated document. We make it clear to users that the REST API is constantly changing and a relevant change may not be communicated.

    Changes were recently made to the invoices and customers list in line with our spring release on the 6th of April.

    Thanks,

    Tom

  • Christina Spencer commented
    10 Jan, 2017 09:18am

    Paul - I am also eager to be able to use the REST API - and would be happy to use it even in an incomplete state because it would be used for semi-manual processing in the first instance, for a small functionality set - to look at sales on our website that have not yet been added to KF - I have it set up in its current incarnation (SOAP) so any anomalies are reported to me for investigation. The showstopper with REST for us is the authentication method.

  • Jerome Rigaud commented
    10 Jan, 2017 09:18am

    Hi Tom
    is there any ETA on this? we are considering the prep work on SOAP and would like to establish how to best schedule our efforts and if we should wait (or not) to rather use the REST.

  • Load older comments
  • and 6 more