Legacy Dev Forum Posts

 View Only

Sign Up

  • 1.  OAuth client_credentials

    Posted 06-05-2025 18:14

    Rod | 2018-10-08 19:52:33 UTC | #1

    I am trying to receive token to make API calls, for so I am using clientcredentials grant, after configuring the OAuth service (at:https://apps.mypurecloud.com.au/directory/#/admin/integrations/oauth) to create a new app and generate the credentials I receive the following JSON: {"error":"invalidclient","description":"authentication failed"}

    The command line that I have used to test was:

    curl -k -v -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Basic BASE64(my-id:my-secret)" -d "granttype=clientcredentials" -X POST https://login.mypurecloud.com/oauth/token

    I have seen some other people with the same problem, but the solution was not there or wasn't clear for me, so please can anyone help me on that?

    Regards,

    -Rod

    crespino | 2018-10-08 17:50:06 UTC | #2

    Rod,

    I think your trouble may stem from the Authorization header that you are trying to send. In Client Credentials grant you need to get your client id and secret from the Integrations->OAuth section of PureCloud Admin. You'll need to concatenate the client id and secret together, separated by a ':', so it looks like this "<clientidhere>:<clientsecrethere>". Then you need to base64 encode that concatenated string.

    As an example if you have the following:

    Client ID: 'open' Client Secret: 'sesame'

    If you base64 encode the string 'open:sesame', you get 'b3BlbjpzZXNhbWU='. Then your HTTP Authorization header will look like this:

    Authorization: Basic b3BlbjpzZXNhbWU=

    Here is more info on client credentials grant here: https://developer.mypurecloud.com/api/rest/authorization/use-client-credentials.html

    Hope that helps.

    Rod | 2018-10-08 19:52:16 UTC | #3

    Hi Crespino,

    Thanks for answering. What you said is exactly what I have done. I got the "client-id"+:+"secret" from OAuth, then encoded that string using Base64 encoder. Forming the string "Authorization: Basic <BASE64 ENCODED HERE>". I have used exactly what is in curl in my question and also tried using genesys sample code to fetch the token, but always fails with JSON: {"error":"invalid_client","description":"authentication failed"}.

    So, I am sorry but you did not answer my question.

    crespino | 2018-10-08 20:24:00 UTC | #4

    As far as I'm aware there is no BASE64() function built into CURL. So you have two options.

    1. Use the '-u username:password' command line parameter for CURL. So your request would look like this:

    curl -k -v -H "Content-Type: application/x-www-form-urlencoded" -u my-id:my-secret -d "granttype=clientcredentials" -X POST https://login.mypurecloud.com/oauth/token

    1. Use the '-h "Authorization: Basic <base64encoded my-id:mysecreot>" command line parameter for CURL. You use this parameter you would have to first use an online base64 encoder like https://www.base64encode.org to encode the "my-id:m-secret" string. Then you would have to paste that base64 encoded string into the request. Your request would look like this, but using your base64 encoded credentials in the header:

    curl -k -v -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Basic b3BlbjpzZXNhbWU=" -d "granttype=clientcredentials" -X POST https://login.mypurecloud.com/oauth/token

    Both of those examples work for me and return an access token.

    Rod | 2018-10-08 20:36:01 UTC | #5

    Dear Crespino,

    thanks again for your answer. I just got the answer for my problem and I am writing to clear that for other colleagues that could get the same problem. So the answer is:

    • Once I am in Australasian region, I need to insert .au in the end of my request for token, such as in:

    curl -k -v -H "Content-Type: application/x-www-form-urlencoded" -H "Authorization: Basic ENCODED-STRING" -d "granttype=clientcredentials" -X POST https://login.mypurecloud.com.au/oauth/token

    Notice the url has been changed "https://login.mypurecloud.com.au/oauth/token", so now it is working like a charm.

    Thanks again for your help,

    Regards,

    -Rod

    crespino | 2018-10-08 21:03:23 UTC | #6

    Great! Glad you got it working.

    system | 2018-11-08 21:09:32 UTC | #7

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 3687



Related Content