Admanage AI Ad Management API

What authentication does the Admanage AI Ad Management API use?

The API uses HTTP bearer authentication. The token is supplied in the Authorization header on every request. Through Jentic, the token is stored in the vault and injected at execution time so the agent never sees the raw secret.

Can I launch ads on multiple networks in one call with the Admanage AI API?

Yes. POST /launch accepts a batch payload that fans out ad creation across Facebook, TikTok, Snapchat, Pinterest, Google, AppLovin, and Taboola. Use GET /batch-status/{id} to confirm each network's launch completed.

How do I duplicate a Google Ads campaign with the Admanage AI API through Jentic?

Search Jentic for 'duplicate google ads campaign', load POST /google-ads/duplicate-campaign, and execute it with the source campaign ID. This is faster than scripting against the underlying Google Ads API directly.

What are the rate limits for the Admanage AI API?

The OpenAPI specification does not publish numeric rate limits. Admanage applies limits server-side; HTTP 429 responses indicate throttling. Through Jentic, retry behaviour with backoff is set in the execution request.

Can I update creative assets on Google Ads Performance Max with the Admanage AI API?

Yes. POST /google-ads/add-text-assets, /add-assets, /update-assets, and /remove-assets manage text and media assets on Performance Max asset groups without using the Google Ads UI.

Can I limit what my agent is allowed to do with the Admanage AI Ad Management API?

Yes. Because you run Jentic One yourself and choose which Admanage AI operations to import, you decide exactly what the agent can call, so you can allow it to launch from a draft with POST /launch/from-draft or read campaigns with GET /google-ads/campaigns while leaving everything else out. Since Admanage AI takes launch and campaign targets in the request body, destructive or scaling actions like POST /google-ads/campaigns/toggle-status or POST /google-ads/duplicate-campaign stay unavailable unless you explicitly include them. The bearer token is held by your own Jentic One instance and injected only for the operations you permit, so the agent cannot reach endpoints you did not grant.