canonical: https://jentic.com/apis/admanage.ai/admanage

# Admanage AI Ad Management API

Jentic publishes the only available OpenAPI specification for the Admanage AI Ad Management API, keeping it validated and agent-ready. The Admanage AI API exposes 61 endpoints for launching, duplicating, renaming, and reporting on ads across Facebook, TikTok, Snapchat, Pinterest, Google Ads, AppLovin/Axon, and Taboola from a single integration. It also covers media library management, drafts, and automation rules. Use it to consolidate ad operations for performance teams running campaigns on multiple networks at once.

## For AI agents

Launch and manage ad campaigns across Facebook, TikTok, Snapchat, Pinterest, Google, AppLovin, and Taboola through a single API, including duplicating, renaming, and toggling campaign status.

## Scope

Does not handle email marketing, organic social posting, or web analytics - use for cross-platform ad launching, scaling, and asset management only.

## Capabilities

- Launch ad batches across Facebook, TikTok, Snapchat, Pinterest, Google, AppLovin, and Taboola in one call
- Duplicate Google Ads campaigns, ad groups, and ads to scale winning creatives
- Toggle Google Ads campaign status to pause underperformers programmatically
- Add, remove, and update text and media assets on Google Ads asset groups
- Track batch launch status to confirm cross-platform deployments completed
- Launch ads from existing drafts to standardise creative templates across teams

## Use cases

### Cross-Platform Campaign Launch

Performance marketing teams launch the same campaign creative across Facebook, TikTok, Snapchat, Pinterest, Google, AppLovin, and Taboola through POST /launch instead of building one integration per network. Batch status can be polled with GET /batch-status/{id} to confirm each platform completed. This cuts launch time from hours of manual UI work to a few API calls.

Example prompt: Launch a batch with creative ID 778 across Facebook, TikTok, and Google Ads via POST /launch and poll GET /batch-status/{id} until it returns completed

### Google Ads Scaling Operations

Growth teams scale winning Google Ads campaigns by duplicating campaigns, ad groups, and ads through dedicated POST /google-ads/duplicate-campaign, /duplicate-ad-group, and /duplicate-ad endpoints. Renaming and status toggles are exposed as separate operations so an agent can build a structured scaling workflow rather than scripting against the Google Ads API directly.

Example prompt: Duplicate Google Ads campaign 4421 via POST /google-ads/duplicate-campaign and rename the copy to 'US-2026-Q3' via POST /google-ads/campaigns/rename

### Asset Management on Google Ads Asset Groups

Creative ops teams add, remove, and update text and media assets on Google Ads Performance Max asset groups via POST /google-ads/add-text-assets, /add-assets, /remove-assets, and /update-assets. This automates routine refreshes that otherwise require navigating the Google Ads UI per asset group.

Example prompt: Add three new headline text assets to Google Ads asset group 9912 via POST /google-ads/add-text-assets

### Agent-Driven Multi-Platform Ad Ops via Jentic

AI agents can run multi-platform ad operations through Jentic without integrating each underlying ad network. Bearer tokens for Admanage are kept in your Jentic One instance, and intent search resolves to the right Admanage endpoint so the agent does not need to learn the API's 61-endpoint surface up front.

Example prompt: Search Jentic for 'pause google ads campaign', load POST /google-ads/campaigns/toggle-status, and execute it for campaign 4421 with status paused

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /launch | Launch a batch of ads across networks |
| POST | /launch/from-draft | Launch ads from an existing draft |
| GET | /batch-status/{id} | Check launch batch status |
| GET | /google-ads/campaigns | List Google Ads campaigns |
| POST | /google-ads/campaigns/toggle-status | Pause or enable a Google Ads campaign |
| POST | /google-ads/duplicate-campaign | Duplicate a Google Ads campaign |

## Key resources

- **Launch** — Cross-platform launch operations and batch status tracking
- **Google Ads Campaigns** — List, toggle, rename, and duplicate Google Ads campaigns
- **Google Ads Asset Groups** — Add, remove, and update text and media assets on Performance Max asset groups
- **Drafts** — Save campaign drafts and launch them later
- **Media Library** — Store and reference media assets used across networks
- **Automation Rules** — Configure rules that trigger campaign actions automatically

## Why Jentic

- **Setup:** Wiring the Admanage AI API by hand means handling its bearer token auth and polling batch-status ids yourself across multiple ad networks. Through Jentic you install once, import Admanage AI from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Admanage AI takes launch and campaign targets in the request body, so you limit the agent to the operations it needs, such as launching from a draft or reading Google Ads campaigns. Because you pick the operations, a status toggle or duplicate stays out unless you include it.
- **Credential handling:** Your Admanage AI bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'launch ads across networks' or 'duplicate a Google Ads campaign', and Jentic returns the matching Admanage AI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook Graph API** — Direct access to Facebook ad accounts that Admanage AI orchestrates against.
- **Google Display & Video 360 API** — Google's premium DSP API for cross-platform display and video buys.
- **Snapchat Marketing API** — Snapchat's native marketing API used as one of Admanage AI's downstream targets.

## FAQ

### Why is there no official OpenAPI spec for Admanage AI Ad Management API?

Admanage AI does not publish an OpenAPI specification. Jentic generates and maintains this spec from admanage.ai/api-docs so AI agents and developers can call it via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### 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.
