search

redguava / cliniko-api

The API for Cliniko
73 stars 39 forks source link

Add Payments endpoint. #90

Open ghost opened 9 years ago

ghost commented 9 years ago

Hi,

The payments endpoint would be extremely useful for generating reports that Cliniko can't generate at the moment regarding daily payments seperated by practitioner, etc.

Happy to expound on use cases if needed.

Regards, Oliver Frye IT Manager Mary Street Wellness

jfriedlaender commented 8 years ago

Not what you are asking for, but we have just added invoice items to the API. It might be useful.

https://github.com/redguava/cliniko-api/blob/master/sections/invoice_items.md.

Cameron-InterlockIT commented 8 years ago

We would also love to see a payments endpoint added, in our case we are integrating with an external accounting system, and not being able to accurately move individual payments over is a big roadblock.

slackhack commented 8 years ago

I vote for it as well. I am writing some reports for a client and a payments API is really something we need.

ducas commented 7 years ago

+1

rocface commented 7 years ago

+1

blakemlloyd commented 6 years ago

Any updates on this? Would be very useful

JohnColvin commented 6 years ago

We don't have any significant news on this. We've been reworking on the financial stuff to be easier to work with and to build some new features on it. We need to be sure everything is as it should be before we etch into the API stone.

We know this is a big one for people and getting it in order on our side is a big one for us, too.

hagen commented 6 years ago

Any update on this?

bpinto commented 6 years ago

We've got nothing on this yet, sorry.

hagen commented 5 years ago

@fcbaconguis tracking on this issue. No updates yet, sorry.

robheaydon4 commented 4 years ago

+1

fergusmac commented 4 years ago

+1 that this would be very useful.

MasonD commented 3 years ago

+1 this is a pretty huge hole in the api preventing integration with accounting software.

IsaacInsoll commented 3 years ago

+1. Nookal has had this in their API forever, I'm surprised it's not an option for Cliniko.

IvanBalakirev commented 2 years ago

+1 Also, need payments!

bensaine commented 1 year ago

This issue is 8 years old. This truly limits what can be done with the API. I've been waiting three years for this to automize our billing. At this point, I am considering simply using a web scraper and doing everything in the browser. Please let me know if this feature is still far out so I can plan accordingly.

IsaacInsoll commented 1 year ago

This issue is 8 years old. This truly limits what can be done with the API. I've been waiting three years for this to automize our billing. At this point, I am considering simply using a web scraper and doing everything in the browser. Please let me know if this feature is still far out so I can plan accordingly.

If you do build a scraper please share what you develop if it's possible :)

JohnColvin commented 1 year ago

@bensaine this feature is still far out

antoinelamy commented 5 months ago

Please

bensaine commented 5 months ago

I was actually able to develop a browser extension which injects an iframe that can create, edit, and modify payments programmatically, which circumvented this issue. But this may only be a solution for my use case. If only there was an endpoint, everything would be so much easier.

juanjsebgarcia commented 3 weeks ago

image

We've started looking at alternatives to get off Cliniko, this single feature is costing us a fortune in near-mindless button clicking for staff. No one enjoys it, it's a bad use of time.

bensaine commented 3 weeks ago

Open-source the code and we'll code the feature ourselves, can't be that hard ! 😆 When internal priorities don't align with customer priorities, you lose customers. An inability to execute on this (almost 10 years!) doesn't exactly inspire confidence in your product, your team, your operations. It just leaves a bad taste.

jfriedlaender commented 3 weeks ago

Not to discount the need for this, but our priorities directly align with customer priorities, it's our only motivation. We are a privately own company that is entirely supported by our customers subscription fees, we work for them.

We have a lot more information at our disposal to what is important for our customer base than you'd see from the outside, and we do our best to balance this.

We know adding it to the API is needed, and we know it's been a long time. So far the effort to benefit ratio hasn't exceeded other things we've worked on, so it hasn't made it to the top yet.