Question
RestClient and getting OAuth token
Trying to use a RestClient to obtain an OAuth token but I can't get it to work. I've specified input parameters for grant_type, client_id, client_secret and scope. Running the request vis curl returns a token so I know the interface is correct but I can't get the RestClient to work.
curl -i -X "POST" "https://api.xxxxxx.com/availity/v1/token" -d "grant_type=client_credentials&client_id=dxxxxxx&client_secret=xxxxxxxxxx&scope=hipaa"
{ "token_type":"bearer", "access_token":"AAIkZDEzNjBiYTAtOWM4NS00ZmE1LWI1NWMtZjhkNGVmYjk3OWU1c3SJD8BSGJmv5AfK2R9y1gl_73RDJT3Maxln8aHX2GZAbT30l06AzJh9Yi42jpt6EnZmbvhlO4TMZu1_KWaQP4uDUCsn-QOe9DYCWWOk_S66aj4pCJUwQYJ2X0cd0XunplT15e6uAoYVPwm0Pql6VQ", "expires_in":300, "consented_on":1550608142, "scope":"hipaa" }
Suggestions?
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
Pegasystems Inc.
US
This SR was resolved by using a C# script. The issue with this call was that the server rejected UTF-8 formatted calls as insecure and returned a 400 error. We were able to replicate this and check this by monitoring the network traffic for this server. At present Pega Robotics automatically makes all REST calls UTF-8.
Accepted Solution
Pegasystems Inc.
US
This SR was resolved by using a C# script. The issue with this call was that the server rejected UTF-8 formatted calls as insecure and returned a 400 error. We were able to replicate this and check this by monitoring the network traffic for this server. At present Pega Robotics automatically makes all REST calls UTF-8.