Re: 403 error Request had insufficient authentication scopes.

2019-08-06 Thread f s
Hi, Sai Thanks a lot. I got the correct response after recreated the refresh token. I might have made the token without the adwords scope... -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

403 error Request had insufficient authentication scopes.

2019-08-06 Thread f s
I received the correct response in the same request before, why is the error returned? Isn't the Google Ads API's scope just enough? I can't add another adwords scope. What should I do? Request via curl: POST /v1/customers/4939887x/googleAds:search HTTP/1.1 Host: googleads.googleapis.com Develo

Re: How to request EXPANDED DYNAMIC SEARCH AD

2019-07-01 Thread f s
Thank you very match, Nikisha!!! I succeeded in creating the EXPANDED DYNAMIC SEARCH AD. I'm really grateful for you. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You r

How to request EXPANDED DYNAMIC SEARCH AD

2019-07-01 Thread f s
When I create an ad group and then create an ad via curl, I get the response below. HTTP/1.1 400 Bad Request Content-length: 1059 X-xss-protection: 0 X-content-type-options: nosniff Transfer-encoding: chunked Request-id: yzVB1VW3hFtrOsymauYSMA Vary: Origin, X-Origin, Referer Server: ESF -content-

Re: How to make Dynamic Search Ads via curl request

2019-06-30 Thread f s
Thank you, Bharani I found the mistakes and succeeded, but I'm concerned. Just in case, I'll attach a successful pattern and a failed pattern via Node.js. In a campaign request, if I put 'use_supplied_urls_only': true I get an error, otherwise I will succeed. Thank you for your help. -- --

How to make Dynamic Search Ads via curl request

2019-06-28 Thread f s
Hello, Google Ads API Team. I'd like to create the Dynamic Search Ads via curl, so I post the following JSON to: https://googleads.googleapis.com/v1/customers/5838476xxx/campaigns:mutate { 'operations': { 'create': { 'name': 'New campaign', 'advertising_channel

Re: JSON for creating the Ad

2019-06-28 Thread f s
Thank you, Nikisha. Since I was fundamentally wrong, I'll set up another topic. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are s

JSON for creating the Ad

2019-06-27 Thread f s
We're always grateful for Google Ads API Team's help. Well, I'd like to create the Ad via curl, so I post the following JSON to: https://googleads.googleapis.com/v1/customers/5838476xxx/adGroupAds:mutate { 'operations': { 'create': { 'status': 'ENABLED', 'ad_gro

No GoogleAdsClient, No request to API?

2019-06-10 Thread f s
I saw the official PHP library code, but these seem to be optimized for the web service. I'd like to use in batch processing. I have already succeeded in getting access_token alone. $googleAdsServiceClient = $googleAdsClient->getGoogleAdsServiceClient(); Is there a way to request Google Ads API

Re: The endpoint and JSON data when making a POST request using curl

2019-06-03 Thread f s
Thank you so much, Sai. I was able to create an empty campaign. I've put the successful code below. const rp = require('request-promise-native'); const customer_id = 1234567890; const developerToken = '***'; const loginCustomerId = 9876543210; const accessToken = '**

Re: The endpoint and JSON data when making a POST request using curl

2019-06-03 Thread f s
Thanks a lot, and I'm sorry, but I deleted the previous question for a reason. Even if you have sample code, it's hard work... 2019年6月4日火曜日 4時57分27秒 UTC+9 adsapiforumadvisor: > > Hello, > > I see that your request needed below corrections: > >1. The campaign_budget should be a resource name

Re: The endpoint and JSON data when making a POST request using curl

2019-06-02 Thread f s
I'll show you all of the code. 'use strict'; const rp = require('request-promise-native'); const accessToken = ''; // replace correctly const customer_id = 1234567890; // replace correctly const putCampaign = async () => { try { const url = `https://googleads.googleapis.com/v1/cus

Re: The endpoint and JSON data when making a POST request using curl

2019-06-02 Thread f s
I'll show you all of the code. 'use strict'; const rp = require('request-promise-native'); const accessToken = ''; // replace correctly const customer_id = 1234567890; // replace correctly const putCampaign = async () => { try { const url = `https://googleads.googleapis.com/v1/cus

Re: The endpoint and JSON data when making a POST request using curl

2019-06-02 Thread f s
I'll show you all of the code via node.js. 'use strict'; const rp = require('request-promise-native'); const accessToken = ''; // replace correctly const customer_id = 1234567890; // replace correctly const putCampaign = async () => { try { const url = `https://googleads.googleap

Re: The endpoint and JSON data when making a POST request using curl

2019-06-02 Thread f s
I read the indicated document and tried the following code. const url = `https://googleads.googleapis.com/v1/customers/${customer_id}/campaignBudgets:mutate` ; const operations = { 'operations': [ { 'create': { 'name': 'new Budgets 1', 'amount_micros': 10, 'total_amount_micros': 10,

The endpoint and JSON data when making a POST request using curl

2019-05-29 Thread f s
I must use Node.js, curl and JSON, NOT library. So, I need endpoint and JSON data. I'm coding with a test account and I'd like to make one campaign. Could you give me some examples of endpoint and JSON data? for examples: const endpoint = 'https://googleads.googleapis.com/v1/customers/${custome

Will Google APIs support Node.js?

2019-05-15 Thread f s
Will Google APIs support Node.js in the future? Do I need to develop using SOAP by Node.js? -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message becaus