CPAlead Advertiser Campaign API: Offers Banayein aur Manage Karein

CPAlead Campaign API ek verified self-serve advertiser ko code, AI agent, MCP server, ya plugin ka use karke CPA, CPI, aur CPC campaigns ke saath kaam karne deta hai. Ek authorized client current campaign requirements read kar sakta hai, save karne se pehle complete campaign validate kar sakta hai, creative upload kar sakta hai, campaign create kar sakta hai, campaigns list aur retrieve kar sakta hai, version protection ke saath campaign edit kar sakta hai, aur eligible campaign ko explicitly start ya pause kar sakta hai.

Yeh normal advertiser dashboard ka automation companion hai. Agar aap pehle campaign types, tracking, targeting, payouts, caps, funding, review, aur launch ka field-by-field explanation chahte hain, to How to Advertise on CPAlead in 2026: Add and Launch Your First Offer padhein. Jab aap us setup ko structured JSON aur controlled API actions mein express karne ke liye ready ho, tab yeh article use karein.

Campaign API kya kar sakta hai

API abhi archive, delete, bulk-create, ya generic toggle operation provide nahi karta. Archive ya delete ka kaam dashboard workflow rahega. Start aur pause alag actions hain taaki koi person ya AI client delivery change karne se pehle clear confirmation maang sake.

Campaign API aur Offer API Import alag hain

• Campaign API: Ek scoped bearer-token API jo aapke advertiser account mein campaigns validate, create, read, edit, start, aur pause karti hai.
• Offer API Import: Ek alag advertiser-dashboard workflow jo compatible external feed se offers read karta hai aur unke fields ko CPAlead mein map karta hai.

Advertiser API Center in tools ko alag pages par rakhta hai. Sign in karein, Setup → API kholen, phir apne task ke mutabik tool choose karein. Jab aapki apni application, agent, MCP server, ya plugin ke paas already offer data ho aur CPAlead ke saath kaam karne ka structured tareeka chahiye ho, tab Campaign API use karein. Jab CPAlead ko supported offer feed fetch aur map karna ho, tab importer use karein. Kisi integration ko uske kaam se zyada broad token na dein.

Campaign API token banayein

1. Verified self-serve advertiser account mein sign in karein.
2. Setup → API kholen, phir Campaign API select karein.
3. Token ko koi recognizable naam dein, jaise “Campaign validator” ya “My MCP agent.”
4. Expiration choose karein. AI setup ke liye 48-hour option recommended hai; 30-day, 90-day, aur 365-day options bhi available hain.
5. Sirf wahi permissions select karein jo client ko chahiye.
6. Token create karein aur turant copy karein. Page reload hone ke baad CPAlead poora token dobara display nahi kar sakta.
7. Isse trusted client ki secret configuration mein store karein aur task khatam hone par revoke kar dein.

Ek advertiser ke paas 10 active Campaign API tokens tak ho sakte hain. Alag integrations ke liye alag tokens use karein taaki aap permissions limit kar saken, usage review kar saken, aur ek integration revoke karke doosre ko interrupt na karein.

Apna Campaign API token kahan banayein

Campaign API token private API credential hai jo Authorization header mein bheja jata hai. Yeh aapka CPAlead password nahi hai, aur isse CPAlead dashboard mein sign in nahi kiya ja sakta. Sign in karne ke baad Setup → API kholen, Campaign API select karein, aur Create a token form use karein.

Base URL, authentication, aur response format

Authenticated requests token ko HTTP authorization header mein ek baar bhejte hain. Isse URL ya query string mein kabhi na rakhein.

Authorization: Bearer YOUR_TOKEN
Accept: application/json

Neeche diye gaye curl examples ke liye, safer setup yeh hai ki authorization header ko local curl configuration file mein store karein jo source control se exclude ho aur sirf aapke liye readable ho:

# cpalead-auth.cfg
header = "Authorization: Bearer YOUR_TOKEN"
header = "Accept: application/json"

# Restrict the file before using it:
chmod 600 cpalead-auth.cfg

Successful response mein data object ya list ke saath meta hota hai. Metadata mein request_id aur current schema version shamil hote hain, aur pagination, resource version, ya idempotent-replay flag bhi ho sakta hai. Error response mein error object ke saath meta hota hai. Troubleshooting ke liye support ke saath public request_id save karein, lekin kabhi bhi support ko apna bearer token na bhejein.

Step 1: Live requirements read karein

Requirements yeh source of truth hain ki account abhi kya submit kar sakta hai. Inmein current schema aur terms versions, account creation eligibility, supported countries aur devices, field limits, campaign-type rules, pricing ranges, schedules, launch packages, tracking requirements, image rules, aur recommended workflow shamil hain.

curl --config cpalead-auth.cfg \
  "https://www.cpalead.com/api/v1/advertiser/requirements?type=CPA"

Response ko limit karne ke liye type=CPA, type=CPI, ya type=CPC use karein. Old example se schema version, terms version, payout limit, bid, budget, launch package, country, device, ya minimum app version hard-code na karein. Jab server bataye ki koi value ya version out of date hai, requirements dobara fetch karein.

Teen campaign types

• CPA: Declared action ke liye pay karta hai. Tracking URL mein {CLICK_ID} hona chahiye, aur preview URL, conversion goal, daily cap, aur launch package create shape ka hissa hote hain.
• CPI: Install ya configured app event ke liye pay karta hai. Yeh {CLICK_ID} use karta hai aur device platform, tracking method, supported iOS version, aur proxy handling jaise app-oriented choices add karta hai.
• CPC: Valid click ke liye pay karta hai. Isme conversion payout, daily cap, aur launch package ki jagah bid aur daily budget use hota hai.

Sabhi Campaign API money values USD mein hote hain, aur API schedules UTC use karte hain. Returned requirements read karein aur yeh facts request approve karne wale person ko dikhayein.

Step 2: Campaign image upload karein

Create requests remote image URL accept nahi karte. Pehle file ko multipart form data ke roop mein upload karein, phir returned temporary image ID ko image_upload_id mein rakhein.

curl --config cpalead-auth.cfg \
  --request POST \
  --form "[email protected]" \
  "https://www.cpalead.com/api/v1/advertiser/images"

• Accepted sources: JPG, JPEG, PNG, GIF, BMP, aur WebP.
• Maximum file size: 2 MiB.
• Source width aur height: har ek 200 aur 4096 pixels ke beech hona chahiye.
• Stored result: ek non-animated, metadata-free 200×200 WebP crop.
• Unused upload lifetime: 24 hours.
• Outstanding-upload limit: up to 25 current unused image uploads.
• Use: one campaign create ya image update. Different campaign ke liye dobara upload karein.

Validation yeh check kar sakta hai ki image ID aapke account ka hai aur use kiye bina usable rehta hai. Successful campaign write ise consume kar deta hai. Same idempotency key ke saath same completed create ko replay karne par stored result return hota hai; consumed image se second campaign nahi banti.

Step 3: Complete campaign JSON banayein

API strict JSON objects use karta hai. Unknown fields silently ignore karne ke bajay reject kiye jaate hain. Isse AI integration zyada safe hoti hai: misspelled ya invented property accidental campaign setting banne ke bajay visible validation issue ban jaati hai.

Neeche diya gaya CPA example ek template hai, ready-to-submit campaign nahi. Har COPY_FROM_REQUIREMENTS value, image ID, URL, payout, country, cap, aur public description ko apne real offer ke reviewed values se replace karein.

{
  "schema_version": "COPY_FROM_REQUIREMENTS",
  "external_id": "signup-campaign-us-001",
  "type": "CPA",
  "name": "US Account Signup",
  "creative": {
    "title": "Create Your Free Account",
    "description": "Register and confirm your email",
    "conversion_goal": "Create an account"
  },
  "tracking": {
    "url": "https://tracker.example.com/click?click_id={CLICK_ID}",
    "preview_url": "https://www.example.com/signup",
    "gaid_idfa_filler": false
  },
  "targeting": {
    "countries": ["US"],
    "device": "all_devices",
    "tools_only": false
  },
  "pricing": {
    "payout": "0.50",
    "daily_cap": 20,
    "currency": "USD"
  },
  "schedule": {
    "mode": "always",
    "start_time": "00:00",
    "end_time": "23:59",
    "timezone": "UTC"
  },
  "publisher_access": {
    "mode": "all",
    "publisher_ids": []
  },
  "launch_package": {
    "amount": "COPY_FROM_REQUIREMENTS"
  },
  "image_upload_id": "cimg_COPY_FROM_IMAGE_UPLOAD",
  "terms": {
    "version": "COPY_FROM_REQUIREMENTS",
    "accepted": true
  }
}

Important CPA aur CPI tracking rule

Tracking URL mein exact {CLICK_ID} macro hona chahiye. Aapka tracker ya affiliate platform wahan CPAlead jo numeric value inject karta hai use save kare aur conversion ke baad us saved click ID ko CPAlead advertiser postback par return kare. Campaign tracking URL mein CPAlead ka postback URL mat rakhein. Full click-to-postback explanation ke liye public advertiser postback guide use karein.

Step 4: Create karne se pehle validate karein

curl --config cpalead-auth.cfg \
  --request POST \
  --header "Content-Type: application/json" \
  --data-binary @campaign.json \
  "https://www.cpalead.com/api/v1/advertiser/campaigns/validate"

Validation HTTP 200 ke saath data.valid, ek errors list, aur ek warnings list return karta hai. 200 response mein bhi valid: false ho sakta hai, isliye client ko sirf HTTP status ko approval samajhne ke bajay us value ko inspect karna chahiye. Har issue JSON Pointer path ka use karta hai, jaise /tracking/url, /pricing/payout, ya /image_upload_id. AI agent ko sirf indicated field repair karni chahiye, phir dobara validate karna chahiye, aur create permission maangne se pehle final JSON account owner ko dikhana chahiye.

Valid response ka matlab hai payload current validation aur persistence preflight pass kar gaya. Yeh approval, activation, traffic, conversions, ya future eligibility ka promise nahi hai. Writes aur lifecycle actions par real-time review, funding, account access, holds, schedule, cap, aur state checks abhi bhi apply hote hain.

Step 5: Idempotency ke saath safely create karein

curl --config cpalead-auth.cfg \
  --request POST \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: create-signup-campaign-us-001" \
  --data-binary @campaign.json \
  "https://www.cpalead.com/api/v1/advertiser/campaigns"

Create, start, aur pause ke liye Idempotency-Key chahiye jo 8 se 200 visible ASCII characters ke beech ho. Har intended action ke liye naya key use karein. Agar connection fail ho jaye aur aapko na pata ho ki action complete hua ya nahi, to same key ke saath identical action retry karein. CPAlead do baar create ya charge karne ke bajay completed response replay kar sakta hai.

• Same key aur same intent: Completed response meta.idempotent_replay=true ke saath replay ho sakta hai.
• Same key lekin changed details: API idempotency conflict return karta hai.
• Same external ID lekin changed details: API bhi conflict return karta hai.
• Previous request abhi process ho rahi hai: Reported interval ka wait karein, phir same key ke saath same intent retry karein.

Optional external_id create operation ke liye aapka apna stable reference hai. Yeh reconciliation ko easier bana sakta hai, lekin ise different intended campaign ke liye reuse nahi karna chahiye.

Deposit se pehle teen campaigns

Ek advertiser account pehle successful advertiser deposit se pehle total teen self-serve CPA, CPI, ya CPC campaigns create kar sakta hai. Paused, denied, aur archived campaigns bhi count hote hain, kyunki throwaway campaigns create aur archive karke limit bypass nahi karni chahiye. Successful deposit ke baad yeh specific creation limit apply nahi hoti; normal review, balance, payout, budget, aur activation rules phir bhi lagu rehte hain.

Campaigns read aur filter karein

curl --config cpalead-auth.cfg \
  "https://www.cpalead.com/api/v1/advertiser/campaigns?type=CPA&state=paused&page=1&per_page=25"

List endpoint campaign type, public state, updated_since timestamp, page, aur per-page filters support karta hai. Pagination by default 25 campaigns par hoti hai aur per page up to 100 allow karti hai. Public state choices hain active, paused, pending_review, paused_for_funding, cap_reached, outside_schedule, denied, archived, aur unavailable. Archived campaigns sirf tab dikhte hain jab aap explicitly state=archived filter karein.

Campaign resource mein uska ID, optional external ID, version, type, name, creative, tracking, targeting, pricing, schedule, publisher-access setting, image URL, timestamps, aur public state shamil hote hain. State mein review, desired-delivery, delivery-reason, aur capability hints bhi hote hain. Capability hints advisory hain: latest campaign retrieve karein aur real operation response handle karein, kyunki account, funding, review, hold, aur schedule conditions change ho sakti hain.

ETag version protection ke saath update karein

Campaign edits optimistic concurrency use karte hain. Pehle campaign retrieve karein aur exact quoted ETag response header save karein. Phir PATCH request ke saath If-Match mein wahi value bhejein. Yeh kisi ek browser, agent, ya integration ko kahin aur ki gayi newer change ko silently overwrite karne se roakta hai.

# First retrieve the latest campaign and its ETag.
curl --config cpalead-auth.cfg \
  --dump-header campaign-headers.txt \
  "https://www.cpalead.com/api/v1/advertiser/campaigns/12345"

# Then send a reviewed partial update with that exact quoted ETag.
curl --config cpalead-auth.cfg \
  --request PATCH \
  --header "Content-Type: application/json" \
  --header 'If-Match: "COPY_THE_LATEST_ETAG"' \
  --data-binary '{"creative":{"description":"Updated public description"}}' \
  "https://www.cpalead.com/api/v1/advertiser/campaigns/12345"

• No If-Match: API HTTP 428 return karta hai.
• Stale If-Match: API current version metadata ke saath HTTP 412 return karta hai.
• 412 ke baad: Campaign dobara retrieve karein, changes compare karein, approval maangein, aur new ETag ke saath retry karein.
• Unclear network result ke baad: Next update bhejne se pehle campaign retrieve karein.

PATCH sirf public campaign fields accept karta hai. Yeh supplied partial object ko current campaign ke saath merge karta hai aur complete result validate karta hai. Kuch edits ke liye dobara review ya delivery change ki zarurat ho sakti hai, isliye har baar response state padhein.

Start aur pause explicit, bodyless actions hain

# Start an eligible campaign.
curl --config cpalead-auth.cfg \
  --request POST \
  --header "Idempotency-Key: start-campaign-12345-001" \
  "https://www.cpalead.com/api/v1/advertiser/campaigns/12345/actions/start"

# Pause an eligible campaign.
curl --config cpalead-auth.cfg \
  --request POST \
  --header "Idempotency-Key: pause-campaign-12345-001" \
  "https://www.cpalead.com/api/v1/advertiser/campaigns/12345/actions/pause"

Start ya pause karne ke liye JSON body na bhejein—{} bhi nahi. Start karne se pehle campaign, balance, payout ya bid, launch-package effect, countries, devices, schedule, cap ya budget, landing page, aur tracking confirm karein. Response ke baad public state inspect karein; campaign enabled ho sakta hai lekin apni daily schedule ke bahar, funding ke liye paused, cap par, ya delivery ke liye otherwise unable ho sakta hai.

HTTP statuses aur errors jo integration ko samajhne chahiye

HTTP status aur stable error.code ke against automate karein, sirf message wording ke against nahi. Validation details mein path, code, aur plain-English message hota hai. Support se baat karte waqt response request_id include karein.

Rate limits aur responsible retries

Campaign API requests aur authentication rate limited hain taaki advertisers aur service protect ho sakein. Limits change ho sakte hain, isliye request count hard-code karne ke bajay live OpenAPI schema aur response headers use karein. Jab API HTTP 429 return kare, to requests ko immediately repeat karne ke bajay Retry-After ka wait karein. Unchanged public requirements ki pagination, updated_since, aur local caching use karke unnecessary calls avoid karein.

Ek prompt jo aap trusted AI agent ko de sakte hain

Pehle guide aur OpenAPI URL share karein. Token ko agent platform ki private secret settings mein configure karein; is prompt mein real token insert na karein.

Read this CPAlead Campaign API guide and the public OpenAPI schema.

Do not ask me to paste a bearer token into chat. Use only the token configured
privately in the integration. Begin with read and validate operations.

1. Ask whether I am creating CPA, CPI, or CPC.
2. Call the matching requirements endpoint.
3. Ask me for every missing business value and explain any financial,
   tracking, targeting, schedule, review, or delivery effect.
4. Draft strict campaign JSON and validate it.
5. Repair validation errors by their JSON Pointer paths.
6. Show me the final normalized intent and ask for confirmation before
   uploading, creating, updating, starting, or pausing anything.
7. Use a unique idempotency key for create, start, and pause.
8. Retrieve the latest campaign and ETag before an update.
9. After every write, report the campaign ID, public state, request ID,
   warnings, and recommended next step.
10. Never attempt archive or delete because those operations are not in
    the Campaign API.

AI, MCP, plugins, aur code ke liye security checklist

• Least privilege: Read aur validate se shuru karein. Sirf zarurat par ek write permission add karein.
• Short expiry: One-time AI setup task ke liye 48-hour option prefer karein.
• Separate tokens: Har agent ya integration ko uska apna named token dein.
• Private storage: Tokens ko secret settings mein rakhein, URLs, prompts, logs, analytics, screenshots, ya repositories mein nahi.
• Human confirmation: Create, update, start, ya pause se pehle summary required rakhein.
• Safe retries: Uncertain idempotent result ke baad same key aur payload preserve karein.
• Version checks: Latest ETag retrieve kiye bina kabhi update na karein.
• Response checks: Har write ke baad public state aur request ID padhein.
• Revoke promptly: Jab kaam ho jaye ya token leak ho sakta ho to Advertising API page se access remove karein.

Frequently asked questions

Mujhe apna CPAlead API key kahan milega?

Campaign API ke liye credential ko Campaign API token kaha jata hai. Sign in karein aur Advertising → Setup → API kholen, phir Create a token use karein. Token ko turant copy karein kyunki CPAlead poori value sirf ek baar dikhata hai.

Kya API CPA, CPI, aur CPC campaigns create kar sakti hai?

Haan. Har type ka JSON shape strict hota hai lekin alag hota hai. Build karne se pehle us type ke requirements fetch karein.

Kya main AI ko kuch create karne diye bina validate kar sakta hoon?

Haan. Token mein sirf campaigns:validate, aur optionally campaigns:read dein. Requirements aur validation ko create permission ki zarurat nahi hoti.

Kya valid response ka matlab campaign approved hai?

Nahi. Iska matlab current payload validation aur preflight pass karta hai. Review, funding, account access, holds, caps, schedules, aur real-time state abhi bhi apply hote hain.

Kya create se campaign immediately start ho sakta hai?

Haan, account aur campaign par depend karke. Yeh review mein bhi ja sakta hai. Hamesha returned public state inspect karein. CPA ya CPI activation unpaid selected launch package charge bhi kar sakta hai.

Kya main remote URL se image upload kar sakta hoon?

Nahi. Image file ko POST /images ke through upload karein. CPAlead temporary single-use image ID return karta hai.

Kya main ek saath bahut saare offers create kar sakta hoon?

Koi bulk-create operation nahi hai. Har request par ek campaign validate aur create karein, distinct external ID aur idempotency key use karein, aur rate limits aur account creation rules ka respect karein.

Kya API campaign archive ya delete kar sakti hai?

Nahi. Current public API eligible campaigns start aur pause kar sakti hai, lekin archive ya delete expose nahi karti. Archival ke liye advertiser dashboard use karein.

Mere update ko HTTP 412 kyun mila?

Jab aapne ise retrieve kiya tha uske baad campaign change ho gaya. Use dobara lein, newest data review karein, apna intended change merge karein, aur new ETag ke saath retry karein.

Create ne HTTP 409 kyun return kiya?

Stable error code padhein. Possible public reasons mein different data ke saath reused idempotency key ya external ID, koi pehla request abhi process ho raha hona, three-campaign pre-deposit limit, funding ya account restrictions, hold, ya state conflict shamil hain.

Kya meri application ko is article se field limits copy karni chahiye?

Nahi. Yeh article workflow explain karta hai. Aapki application ko live requirements aur OpenAPI schema read karna chahiye taaki current values authoritative rahen.

Machine-friendly Campaign API fact sheet

Read aur validate se shuru karein

Campaign API is tarah design ki gayi hai ki advertiser cautiously shuru kar sake. Trusted agent ko public guide aur schema dein, read aur validation access grant karein, aur use account badle bina request prepare karne dein. Jab JSON sahi ho aur owner review, delivery, aur financial effects ko samajh chuka ho, tab next confirmed action ke liye sirf required write permission add karein.

Token banane ke liye Campaign API in the Advertiser API Center kholen, ya current contract inspect karne ke liye public Campaign API OpenAPI schema kholen. Publisher API documentation alag hai aur publishers ke offers retrieve karne aur reporting ko cover karti hai. Agar response unclear ho, token private rakhein aur public request ID aur campaign ID ke saath Advertiser Support se contact karein.

Kya aapne kisi truti ya is post mein sudhaar ki zarurat dekhi hai? Kripya post link pradaan karein aur humein sampark karein. Hum aapki pratikriya ki saraha karate hain aur samasya ko jald hi sulajhaenge.