Migrated from Redmine #903 | Author: Pavel Merkulov Status: New | Priority: High, I’m very impatient | Created: 2022-07-06
Our company name is “Eurogroup technologies”
We have API request error.
When we try to execute request
GET /admin/bookings?page=1&on_page=100&filter[client_id]=${clientId}&filter[status]=${status}
we receive this error
{
code: 403,
message: ‘Too many attempts please try later.’,
data: ,
message_data:
}
What does it mean? If there are any limits on the number of requests, how can we change them?
We reserve the rights in the case of high volume of bookings to suspend the relevant system momentarily to try to equalize the server load. This can result in some of your users getting a message to try to book again in a few minutes. High load can for example be considered 50 people trying to process a booking with a user account in less than 30 seconds or sending more than 5.000 API requests per day with number of parallel requests to be limited by maximum 2 at same time and not exceed 5 requests per second on common servers. Also, to prevent too high load on servers from individual accounts all subscriptions levels have a maximum number users and providers as per pricing table. Enterprise level allows for higher limits. Common enterprise server has 25.000 per day API requests limit; while dedicated servers allow unlimited requests limited by server specifications.
you need to reuse token, not to get a new one each time
we get a 401 error if we use the previous token. our application logic is to get a new token if we get a 401 error. So we have situation when we have to get new each time.
the problem is that the lifetime of the token we get is initially too short. literally in a few seconds we start getting 401 errors and we have to request a new token. there were no such problems before. this behavior has appeared recently