Adform Seller Campaigns API
★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingnone5 EndpointsREST
For Agents
Create, update, list, and delete sell-side direct-sold campaigns inside Adform's supply-side platform.
Use for: Create a new direct-sold campaign in Adform, List all active seller campaigns for an Adform publisher account, Update the budget for a specific Adform seller campaign, Get the full configuration of an Adform seller campaign by id
Not supported: Does not handle ad creative trafficking, demand-side buying, or post-campaign reporting — use for sell-side direct-sold campaign CRUD only.
The Adform Seller Campaigns API lets sell-side ad operations teams manage direct-sold campaigns and their line items inside the Adform supply-side platform. The five endpoints cover listing, creating, updating, and deleting campaigns at /, plus retrieving a single campaign at /{id}. It is the programmatic equivalent of the Adform UI's Seller Campaigns module, intended for publishers automating booking ingestion from order management systems. Useful when a publisher wants to bridge a CRM-style booking tool with the Adform stack without manual data entry.
Install Jentic One Beta
Connect the Adform Seller Campaigns API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adform Seller Campaigns 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Adform Seller Campaigns API.
List all seller campaigns currently configured for the authenticated publisher account via GET /
Create a new direct-sold campaign with targeting and pacing through POST /
Retrieve a single campaign by id with GET /{id}
Update a campaign's name, dates, or pacing parameters via PUT /{id}
Remove a campaign from the seller workspace using DELETE /{id}
Use Cases
Patterns agents use Adform Seller Campaigns API for, with concrete tasks.
★ Automated booking ingestion from an order management system
When a publisher's sales team confirms a direct-sold deal in a CRM or order management system, an integration job calls POST / on the Adform Seller Campaigns API to create the matching campaign with pacing and targeting parameters. PUT /{id} keeps the campaign in sync if the booking changes. This removes manual re-entry into the Adform UI and shortens the lead time between deal closed and ad live.
On a CRM 'deal won' webhook, call POST / with the campaign name, advertiser, start/end dates, and budget from the deal payload.
Campaign reconciliation and cleanup
Run a nightly reconciliation job that calls GET / to list all seller campaigns, compares them against the canonical list in the order management system, and either updates drifted records via PUT /{id} or removes stale ones via DELETE /{id}. Keeps the Adform workspace tidy and prevents over-delivery on closed bookings.
Call GET / to list all campaigns, diff against the OMS feed, and DELETE /{id} for any campaign whose OMS record is closed.
Campaign reporting front end
Build an internal dashboard for ad ops by polling GET / for the campaign list and GET /{id} for each campaign's pacing configuration. Combined with downstream Adform reporting, this gives the team a single view of which direct-sold deals are live and how their pacing is configured. Replaces context-switching between the Adform UI and the booking spreadsheet.
Call GET / to list campaigns, then GET /{id} for each, and render a table of campaign id, advertiser, dates, and pacing mode.
Agent integration via Jentic
Give an ad-ops agent CRUD tools over Adform seller campaigns through Jentic. The agent receives the five operation schemas at /, /{id} and can answer 'create a campaign for advertiser X with budget Y' or 'pause campaign id 1234' in a single tool call. No client SDK to maintain when the Adform schema changes.
Search Jentic for 'create Adform seller campaign', load POST /, and execute it with the payload supplied by the user.
Key Endpoints
5 endpoints — the adform seller campaigns api lets sell-side ad operations teams manage direct-sold campaigns and their line items inside the adform supply-side platform.
METHOD
PATH
DESCRIPTION
GET
/
List all seller campaigns
POST
/
Create a new seller campaign
GET
/{id}
Retrieve a single campaign by id
PUT
/{id}
Update an existing campaign
DELETE
/{id}
Delete a campaign
GET
/
List all seller campaigns
POST
/
Create a new seller campaign
GET
/{id}
Retrieve a single campaign by id
PUT
/{id}
Update an existing campaign
DELETE
/{id}
Delete a campaign
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adform OAuth client credentials sit in the Jentic vault and are exchanged for short-lived tokens at execution time. Agents never see the raw client secret in their prompts and Jentic handles refresh automatically.
Intent-based discovery
Agents search by intent (e.g. 'create Adform seller campaign') and Jentic returns the matching POST / operation along with the request body schema, so the agent supplies a campaign object without having to read the Adform docs.
Time to first call
Direct Adform integration: 3-5 days for OAuth flow, schema mapping, and idempotent retries. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Adform Seller Campaigns API through Jentic.
What authentication does the Adform Seller Campaigns API use?
The OpenAPI spec for this endpoint set does not declare a security scheme, but in production the wider Adform API requires OAuth 2.0 client credentials. Agents calling through Jentic configure Adform credentials once in the Jentic vault and tokens are refreshed transparently before each call.
Can I create direct-sold campaigns programmatically with this API?
Yes. POST / accepts a campaign payload (advertiser, dates, pacing) and returns the created campaign id. PUT /{id} edits the campaign in place. This is the programmatic equivalent of the Seller Campaigns section of the Adform UI and is intended for publishers automating booking flows.
What are the rate limits for the Adform Seller Campaigns API?
Adform applies platform-wide rate limits in the low hundreds of requests per minute per token; the exact ceiling depends on your contract. Agents that bulk-sync hundreds of campaigns nightly should batch updates and respect 429 responses with exponential backoff.
How do I create an Adform seller campaign through Jentic?
Search Jentic for 'create Adform seller campaign', load the POST / operation under api.adform.com, and execute it with the campaign object — name, advertiser, start and end date, and pacing settings. Capture the returned id for later updates.
How do I list every campaign for reconciliation?
Call GET / with no parameters to retrieve the full list of seller campaigns in the workspace. Use GET /{id} to fetch the full configuration of any specific campaign for diffing against an order management system.
GET STARTED