[#897] API not working consistently

Migrated from Redmine #897 | Author: Nora McWilliam
Status: Feedback | Priority: Immediate, there is BUG! | Created: 2022-06-21


Our API does not seem to be working consistently. I am trying to determine at which end the problem lies. Booking data is feeding through into our system but the results available trigger doesn’t seem to be working and the data is not feeding through once test results are available.

Dmytro Bondarev wrote:

Hi,

It is not clear what is not working. Please provide more details, including error messages, company login, etc.

Nora McWilliam wrote:

Hi there, the API call limit seems to be exhausted all the time. It appears to be a general SimplyBook issue. This is impacting us heavily as clients are now not receiving their signed Covid 19 certificates.

Here is the error message: 403 Forbidden: [{“code”:403,“message”:“Too many attempts please try later.”,“data”:,“message_data”:}]

And the explanation I got from my developer:

The error(or simplybook) is pretty much telling us that we are trying to send requests to them too often. As far as I can see(and understand) this error constantly occurs over a simplybook trigger that makes our system search for a booking and what happens next is we send two requests: one to authenticate, the second to get the booking. For some reason simplybook decides that we have sent too many requests(I assume for X period of time, can’t find by how much exactly) and simply does not let our system use their API for some period of time, thus the missing results from the patients. Now, this didn’t happen before so I’m assuming something changed on their end, again: what exactly? I can’t find that information. This is also probably why some patients receive their results just fine, and also why you guys sometimes can or cannot import them manually.

Nora McWilliam wrote:

Our company login is care24

Dmytro Bondarev wrote:

Hi,
Actually you are trying to get token to often. You should reuse token that you get and then get new access token with refresh token, after it expires.

Nora McWilliam wrote:

How do we know the token has expired. Do we get notified?

Dmytro Bondarev wrote:

Yes, you will get related error with 419 status.

Nora McWilliam wrote:

And how has this been working without any issues since last year? We had this set up for another business as well?

Nora McWilliam wrote:

Did you recently make changes to this?