Genesys Cloud - Main

Hello,

We are planning to create a new OAuth client using the Client Credentials grant type, intended for use by a third-party system.

The purpose of this integration is to enable the third-party system to:
- Create contact lists
- Add and manage contact data within those lists

To support this functionality, the OAuth client will need to be associated with a role that includes, at a minimum, the following permissions:
Outbound > Contact > Add
Outbound > Contact > Edit
Outbound > Contact > View
Outbound > Contact List > Add
Outbound > Contact List > Edit
Outbound > Contact List > View

We can see that all of the above permissions require a Cloud CX 1 license.

Could you please clarify whether the use of OAuth Client Credentials by a third-party system to invoke the relevant Genesys Cloud APIs results in license consumption? If so, could you elaborate on how this licensing is applied in such scenarios?


Best regards,
Orestis Dimitropoulos

Hi Orestis,

I wasn't able to find a Genesys resource that explicitly confirms licensing behaviour for OAuth clients, but based on the documentation available:

Client Credentials is designed for non-user applications and operates outside the context of a user, with access controlled by the roles assigned directly to the OAuth client.
https://help.mypurecloud.com/articles/create-an-oauth-client/

Because of that, my understanding is that the OAuth client itself does not behave like a named user consuming a license. Instead, access is governed by the permissions assigned, and your organisation still needs to be entitled to the underlying outbound functionality those permissions relate to.

For anything contract-specific around licensing, hopefully someone from community might add more to this. Following this post.

Hello Orestis, 

The short answer is that using OAuth Client Credentials doesn't consume any user licenses in Genesys Cloud. That flow is designed specifically for system-to-system communication, so there's no actual user logging in or taking up a seat. It's typically used for things like backend services or integrations, where everything runs in the background without a person attached to it.

The part that can be confusing is the role and permission requirements. Even though certain permissions (like outbound contact access) are tied to licenses in the documentation. The client just inherits roles and permissions so it can make the right API calls, but it doesn't count as a billable user. The main things to keep in mind are making sure your org has the right licenses for the features you're using, assigning the correct roles to the OAuth client, and staying within API rate limits-but from a licensing standpoint.

Cheers, 

Good Day Orestis

This will definitely contribute to your API fair usage policy - https://help.genesys.cloud/articles/genesys-cloud-fair-use-policy/.

Depending on whether you have named, concurrent or one of the other license types, with CX1, 2, 3 or 4. You will get a fixed number of API calls per month and anything above that will be charged as overage.

List of API's - https://developer.genesys.cloud/routing/outbound/

Regards