[#822] API calls suddenly stopped working

Bug Reports
,
1

Migrated from Redmine #822 | Author: Antonio Graterol
Status: New | Priority: Immediate, there is BUG! | Created: 2021-12-09

Hi Guys, I hope your having a excellent day.

I come to you because since yesterday I’m having problems with a routine that has been working since October. The problem ocurrs when trying to do this (any other) API call “https://user-api-v2.simplybook.me/admin/auth”. Yesterday gave the error shown in image1.png and today first showed the error in image2.png and then changed again to the previous error. After a lot of attempts, I barely made through and could update our reports but it still unstable.

I don’t know if has to do with the 2fa because is somehow synched with that event. FYI the 2fa is disabled
Is just us or Is there is some kind of sudden problem with your service?

I’d like to know what I have to do to get this solved asap, our daily reporting depends on it. All the help will be very appreciated :).

Thanks in advance,
Antonio

2

Dmytro Bondarev wrote:

Hi, please provide more information, because we do not see any errors.

3

Antonio Graterol wrote:

Hi Dmitry,

The file image1.png shows a fresh shot of the same error.

Let me tell you more about our routine, it’s based on a google script to fill a google spreadsheet, initially from the downloaded booking and payment transactions reports and then it starts to fetch information for the clients (companies) using the API call URL #1 to fill columns AM to AN (image2.png), API call URL #2 to fill columns AO to AS and API call URL #3 to fill column AT.

API call URL #1: 'https://user-api-v2.simplybook.me/admin/invoices?page=&on_page=100&filter[promotion_instance_id]=&filter[datetime_from]=&filter[datetime_to]=

API call URL #2: 'https://user-api-v2.simplybook.me/admin/promotions/coupons?page=&on_page=100

API call URL #3: 'https://user-api-v2.simplybook.me/admin/bookings?page=&on_page=100&filter[providers]=

Some times it had stopped when it’s starting (while doing the authentication) and in other times it did it the middle of the run, as you can see it in image2.png where the AM and AN columns were filled successfully but AO onwards are empty. The rows >= 58 have older data, this run should have populated the rows less and equal than 57

I can’t find a logical explanation for this behaviour.

Dmitry Bondarev wrote:

Hi, please provide more information, because we do not see any errors.

4

Dmytro Bondarev wrote:

Unfortunately we do not images.

5

Dmytro Bondarev wrote:

We do not see images*

6

Antonio Graterol wrote:

Here you can see the images
https://ibb.co/qNYsbjz - image1
https://ibb.co/m892smX - image2

Dmitry Bondarev wrote:

We do not see images*

7

Dmytro Bondarev wrote:

Please provide your company public page url.
It looks like you are getting token for each API call, but you must reuse token and then refresh , when it expires

8

Antonio Graterol wrote:

Hi Dmitry,

The problem was on my code XD, but your advice on reusing the token led the way to the problem. Thanks for your time and help.

Please be safe and have a nice weekend.

Dmitry Bondarev wrote:

Please provide your company public page url.
It looks like you are getting token for each API call, but you must reuse token and then refresh , when it expires