Error:"unauthorized_client"

[伊藤大稀]

Hello,

I received an unauthorized_client error when executing the following command.

curl \

 --data "grant_type=refresh_token" \

 --data "client_id=CLIENT_ID" \

  --data "client_secret=CLIENT_SECRET" \ 

  --data "refresh_token=REFRESH_TOKEN" \

https://www.googleapis.com/oauth2/v3/token

{

  "error" : "unauthorized_client"

}

OAuth verification has not been completed yet, is it related to the above error?
Are there any other possible causes?

Thanks.

-----------------------------------------------------------------------------------------
もし、このメッセージが誤って貴殿に送信されたと思われる場合には、
機密情報を含んでいる可能性もありますので、どなたにも転送せず、
付属したファイルも含めて削除していただくとともに、発信者にその旨を
お伝えいただきますようお願いいたします。
This email may be confidential or privileged.
If you received this communication
by mistake, please don't forward it to anyone else,
please erase all copies and documents,
and please let me know that it went to the wrong person.
Thank you very much.
-----------------------------------------------------------------------------------------

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

To analyse this 'Authorization' issue further could you please provide us with the below details.

• Can you please execute customers.listAccessibleCustomers and provide us complete API request and response logs, you may also check this API documentation for more information. If you are using any programming language please check sample code for List Accessible Customers here.
• The user email you used for authentication.
• Provide the Google Ads API endpoint that you are using.

You can send the details via Reply privately to the author option, or direct private reply to this email.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02tIzOV:ref" (ADR-00235180)

Thanks,
 

Google Ads API Team

 

[Alex Gunner]

OAuth verification does not need to be completed for this. Are you using a MCC test account with your test developer token?

[Google Ads API Forum Advisor]

Hi,

To check what and where went wrong, at least can you provide us with the complete API logs (request and response with request-id and request header) generated at your end when you authorize the client via the API call? so that we can check from our end and get back to you.