Install Jentic One Beta

Connect the Admanage AI Ad Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Admanage AI Ad Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadmanage.ai%2Fadmanage" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadmanage.ai%2Fadmanage" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Admanage AI Ad Management API.

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

GET STARTED

Start building with Admanage AI Ad Management API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Admanage AI Ad Management API for, with concrete tasks.

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

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.

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.

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.

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

61 endpoints — jentic publishes the only available openapi specification for the admanage ai ad management api, keeping it validated and agent-ready.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Admanage AI Ad Management API through Jentic.

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.

Admanage AI Ad Management API

Name: Admanage AI Ad Management API
Brand: Admanage AI Ad Management API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingAdvertisingbearer61 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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

Use for: I want to launch the same creative on Facebook, TikTok, and Google in one batch, Duplicate a winning Google Ads campaign and rename it for a new region, List all Google Ads campaigns for the active account, Pause a Google Ads campaign whose ROAS has dropped

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

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.

Jentic One on Github View OpenAPI Document

Connect the Admanage AI Ad Management API to your agent

Capabilities

Start building with Admanage AI Ad Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Admanage AI Ad Management API