[#280] "Endpoint: getBookings. Method not found"

Bug Reports
,
1

Migrated from Redmine #280 | Author: Gennadiy Fayrushin
Status: New | Priority: Immediate, there is BUG! | Created: 2018-11-06

Suddenly we noticed what this method is no longer available for us for some reason. Цhat happened?
?

2

Dmytro Bondarev wrote:

Please provide company login and company URL.

3

Gennadiy Fayrushin wrote:

My driving academy

4

Redmine Admin wrote:

Thank you for quick report. Fixed.

5

Gennadiy Fayrushin wrote:

Ok, it works now, but we have payment_status: null in responses

6

Redmine Admin wrote:

We are making big update now and migrating data. Should be ok in very soon when data migration finished.

7

Gennadiy Fayrushin wrote:

We still have a big problem after that update. All bookings created after your update have no payment processor string information (we are using the confirmBookingPayment method). All bookings created after the day now have just payment_status=null too.
We just can’t distinguish paid and unpaid bookings at all

8

Gennadiy Fayrushin wrote:

Any news?

(Short original content)

9

Dmytro Bondarev wrote:

Hello! We released big update with new payments, with invoices.
The public API for invoices is not ready yet.
We will allow to use confirmBookingPayment as it was, but actually this method deprecated for a long time.

10

Gennadiy Fayrushin wrote:

You mean you disabled an old endpoint and dont provide the new one? What can we do now to resolve the issue?

11

Dmytro Bondarev wrote:

we didn’t disable it yet.
we will fix this method and you will be able to use it.

12

Gennadiy Fayrushin wrote:

And also, I’m using the next link to check API endpoints. It is not deprecated here

13

Gennadiy Fayrushin wrote:

Is there any link where I could find such updates in advance? And a link with deprecated methods?

14

Dmytro Bondarev wrote:

We will update this page.

15

Gennadiy Fayrushin wrote:

Ok. Please let us know when confirmBookingPayment is fixed

16

Gennadiy Fayrushin wrote:

When it will be fixed? We still have payment_status: null and no information about paymentproccessor

17

Dmytro Bondarev wrote:

Hello! it will be available this week. sorry for delay