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
  • Under Review
  • Jan 10, 2017

    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
  • Paul Jansen commented
    January 10, 2017 09:18

    This is very very disappointing in two ways

    1. That there has been no progress

    2. that you failed to respond to the points I made and just replied with a message that basically says "Go away, we're not interested"

    As it stands there is no sensible way to monitor progress and changes.

    If there is no end in sight can you not at least add a last modified date to each item in the list on https://www.kashflow.com/developers/rest-api/. As it stands I have to go though each and every one to find out what has changed (unless I have missed something) which is ridiculous.

    In April 2015 the first comment on this topic stated that the API is roughly 50% complete, can you really not update us on whether any progress at all has been made since then?

    I do wonder if I am completely wasting my time even having this conversation. I certainly don't fell like a valued customer.

  • KashFlow Product Manager commented
    January 10, 2017 09:18

    Hi Paul/Jerome,

    Thank you for getting in touch. There are currently no further updates to share on the REST API unfortunately. As discussed, we will continue to release all new functionality onto REST and update the information provided to our users at https://www.kashflow.com/developers/rest-api/.

    However, we will not be releasing a production REST API in the near future.

    Many thanks

  • Paul Jansen commented
    January 10, 2017 09:18

    Tom,

    I have to admit in my opinion this is getting ridiculous. 8 months on and still no progress on a production REST API.

    Is it not possible to state that certain functions are stable and to provide notification of any changes to these "Stable" aspects, whilst continuing to allow for "continuous changes" of other aspects/areas?

    I have to admin to being very frustrated by the lack of progress to the extent that I am looking at your competitors who do have a production REST api and wondering whether I should consider switching..,.

  • Jerome Rigaud commented
    January 10, 2017 09:18

    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.

  • Christina Spencer commented
    January 10, 2017 09:18

    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.

  • KashFlow Product Manager commented
    January 10, 2017 09:18

    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

  • Paul Jansen commented
    January 10, 2017 09:18

    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
    January 10, 2017 09:18

    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
    January 10, 2017 09:18

    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
    January 10, 2017 09:18

    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
    January 10, 2017 09:18

    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
    January 10, 2017 09:18

    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
    January 10, 2017 09:18

    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.

  • Paul Jansen commented
    January 10, 2017 09:18

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

  • Oliver commented
    January 26, 2017 01:38

    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.....

  • Christina Spencer commented
    February 6, 2017 13:41

    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 
     
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar
  • Gravatar