Hi Shipra,
Most probably, the budget was given a name before it was attached to a campaign, like many of our samples do. In that case, the budget has its own name. I tested a scenario in Google Ads Search with a budget name and without a budget name and found this to be true. This works in v11 REST Interface, you can try with a budget name, then without a budget name and here's a
recipe for an access token :
curl -i --request POST https://googleads.googleapis.com/v11/customers/<CID>/googleAds:mutate \
--header "Content-Type: application/json" \
--header "login-customer-id: <LCID>" \
--header "developer-token: <DT>" \
--header "Authorization: Bearer <AT>" \
--data '{
"mutateOperations": [
{
"campaignBudgetOperation": {
"create": {
"resourceName": "customers/<CID>/campaignBudgets/-1",
"status": "ENABLED",
"deliveryMethod": "STANDARD",
"period": "DAILY",
"name": "testinjune14-456",
"type": "STANDARD",
"amountMicros": "50000000",
"explicitlyShared": false,
},
},
},
{
"campaignOperation": {
"create": {
"status": "PAUSED",
"advertisingChannelType": "SEARCH",
"networkSettings": {
"targetGoogleSearch": true,
"targetSearchNetwork": true,
"targetContentNetwork": false,
"targetPartnerSearchNetwork": false
},
"biddingStrategyType": "MANUAL_CPC",
"manualCpc": {
"enhancedCpcEnabled": true
},
"geoTargetTypeSetting": {
"positiveGeoTargetType": "PRESENCE_OR_INTEREST",
"negativeGeoTargetType": "PRESENCE"
},
"paymentMode": "CLICKS",
"name": "testinjune14",
"campaignBudget": "customers/<CID>/campaignBudgets/-1",
"startDate": "2022-06-13",
"endDate": "2022-09-08",
},
},
},
],
"responseContentType": "MUTABLE_RESOURCE"
}
'
Regards,
 |
| Aryeh |
| Google Ads API Team |
|
|
| |

ref:_00D1U1174p._5004Q2bvp9Q:ref