Migrated from Redmine #978 | Author: Mathieu Laurent Status: Closed | Priority: High, I’m very impatient | Created: 2022-12-01
I’m part of a company which uses SimplyBook.me to manage and reserve slots with different websites.
There are minimum 3 simultaneous websites which uses it because we need to use the same service id on every website.
Therefore, each website sends api requests to sbm to authentify and reinitialize connection tokens.
Quickly, we had errors 403 with the message : ‘Too many attempts please try later.’
The limit of the number of simultaneous connections seems very low, is it possible to increase or remove it ?
Or is there another way to avoid these errors ?
Many thanks in advance you for your help,
Best regards
That’s what we do. Currently, each website uses its own token and reinitialize it every 20mn.
The problem doesn’t seems to come from that, but maybe because there are too much reinitializations from different websites.
But we can’t use the same token with each website.
So we use 1 token per website, and when websites reinitialize their token at the same time, the issue appears.
such way is not supported, you can create 3 simplybook accounts, one per site or use one server to get and cache tokens and spread it across your sites
Hello, I am working with Mathieu Laurent, as project manager managing the booking topic for our webapp. Such restriction is not hearable, we have switched to the SBM pro solution and are deploying each of our site with a booking system, and each of our site as a few website using the same SBM account by integrating its API. We cannot use multiple account for the same website since the services/providers are shared, this is one of the purpose of having an API interface …
You can refer to Irene our contract manager at SBM.
Hi, please explain why you are not able to reuse token?
Even if you have many websites you can use common place to store token.
However if you still need to generate many tokens, please enable Strict password policy custom feature and configure it with unlimited login attempts.
Please contact your account manager if you have more questions.
Yes but, at the moment the it had been implemented each of our website has its own backend that trigger the auth token call. This should change in the future, but at the moment we don’t have a choice.
Thank you for the info, we’ll try it.
Could you please give us the precise limitation on theses calls ? How many calls every time period ?