We are a 3rd Party Bot company and integrating with Genesys using Open messaging platform. For this we have created Bearer token using ClientId and ClientSecret. But the rate limit is set to 300 request per mint. One of the suggestion from Genesys Consultant was to create a pool of tokens using using different `clientId(s)` and `clientSecret(s).

We tried it out by generating 3 OAuth tokens using 3 different clientIds and clientSecrets. We found that If one of the generated tokens exhausted its limit of 300 requests/min other tokens also sent error code 429(Too many requests) as the response.

This is an issue because now if we were to have a pool of tokens, which were generated by different Oauth Clients(using different clientIds and clientSecrets) if one of the tokens would breach the limit, the other tokens will be considered to have breached it as well.
#Integrations

If they are different oAuth Clients, then they should not share rate limits, so if that really is happening then you need to reach out to Support.

That being said, 300 a minute is 5 a second - are you hitting that?

You can try caching the bearer token and its validity time frame, for instance in a Data Table the token and expiration date/time.

At the time to request the token, check first if there is already a token, if token it's not expired then use it instead of requesting a new one.

If token is expired, then start the process to request a new one, save it in the Data table with its new expiration date/time and use the new one.

Let's say if token is valid for 15minutes, depending on call traffic, this should reduce the number of times the flow requests a token.

------------------------------
Camilo Montes
i3Vision Technologies Inc.
------------------------------

Original Message:
Sent: 08-02-2022 16:43
From: Paul Simpson
Subject: Rate Limit issue with Bearer tokens

If they are different oAuth Clients, then they should not share rate limits, so if that really is happening then you need to reach out to Support.

That being said, 300 a minute is 5 a second - are you hitting that?

removed the question, realized this question was old

------------------------------
Jan Heinonen
Contact Center Specialist
GlobalConnect AB
------------------------------

Original Message:
Sent: 07-20-2022 20:47
From: Shail Gupta
Subject: Rate Limit issue with Bearer tokens

We are a 3rd Party Bot company and integrating with Genesys using Open messaging platform. For this we have created Bearer token using ClientId and ClientSecret. But the rate limit is set to 300 request per mint. One of the suggestion from Genesys Consultant was to create a pool of tokens using using different `clientId(s)` and `clientSecret(s).

We tried it out by generating 3 OAuth tokens using 3 different clientIds and clientSecrets. We found that If one of the generated tokens exhausted its limit of 300 requests/min other tokens also sent error code 429(Too many requests) as the response.

This is an issue because now if we were to have a pool of tokens, which were generated by different Oauth Clients(using different clientIds and clientSecrets) if one of the tokens would breach the limit, the other tokens will be considered to have breached it as well.
#Integrations