adhook.io API
Agent-ready OpenAPI document · curated by JenticMarketingAdvertisingbearer138 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Schedule and publish social posts, create and monitor paid ad promotions, manage client subtenants, and build targeting templates. Read calendars, counts, and statistics to track campaign output.
Use for: Schedule a social post for next Tuesday across our connected channels, Create a paid promotion for the new product launch, List all promotions running for a client subtenant, Find the posts published this week and their engagement counts
Not supported: Does not handle ad-creative design, payment processing, or website analytics. Use for social publishing and ad-campaign management only.
Jentic publishes the only available OpenAPI specification for adhook.io API, keeping it validated and agent-ready. The adhook.io API manages multi-channel social media and advertising for agencies and brands. It covers scheduling and publishing posts, running paid promotions across ad channels, organizing client subtenants, tracking influencers and their listings, and building reusable targeting templates.
Install Jentic One Beta
Connect the adhook.io API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the adhook.io 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadhook.io%2Fadhook" | sh2
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%2Fadhook.io%2Fadhook" | 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 adhook.io API.
Schedule and publish social posts across connected channels from one queue
Create and manage paid advertising promotions with budgets and targeting
Organize client accounts as subtenants for agency-style multi-brand management
Track influencers and their listings for influencer-marketing campaigns
Build reusable targeting templates and apply them across promotions
Read post calendars, counts, and statistics to monitor campaign output
Use Cases
Patterns agents use adhook.io API for, with concrete tasks.
★ Agent-Managed Social Publishing
An AI agent can take a content brief, schedule posts across the channels connected in adhook, and confirm what is queued. Because adhook exposes calendars and post counts, the agent can check for gaps in the schedule and fill them without a human opening the dashboard. Through Jentic the agent discovers the create-post operation by intent and runs it with the token injected at call time.
Schedule a post promoting Friday's webinar to all connected channels at 9am
Automated Ad Promotion Management
Marketing teams use adhook to run paid promotions across ad channels. An agent can create a promotion from a campaign brief, apply a saved targeting template, and monitor its statistics, escalating to a human only when spend or performance crosses a threshold. This keeps routine campaign operations moving without manual clicks.
Create a promotion for campaign X with a 500 euro budget and the standard targeting template
Agency Multi-Client Operations
Agencies manage many brands in adhook as separate subtenants. An agent scoped to one subtenant can list that client's promotions and posts, report total activity, and prepare the next week's schedule, keeping each client's work isolated. This suits agencies that want per-client automation without cross-client access.
List every active promotion under the subtenant for client Acme and report total spend
Key Endpoints
138 endpoints — jentic publishes the only available openapi specification for adhook.
METHOD
PATH
DESCRIPTION
GET
/v1/posts
List scheduled and published social posts
POST
/v1/posts
Create a social post
GET
/v1/promotions
List advertising promotions
POST
/v1/promotions
Create an advertising promotion
GET
/v1/subtenants
List client subtenant accounts
POST
/v1/targetingTemplates
Create a reusable targeting template
GET
/v1/posts
List scheduled and published social posts
POST
/v1/posts
Create a social post
GET
/v1/promotions
List advertising promotions
POST
/v1/promotions
Create an advertising promotion
GET
/v1/subtenants
List client subtenant accounts
POST
/v1/targetingTemplates
Create a reusable targeting template
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the adhook.io API by hand means obtaining a bearer token, setting the Authorization header on every request, and mapping its 138 operations across posts, promotions, and subtenants yourself. Through Jentic you install once, import adhook from the API Directory, store the token once, and your agent calls it.
Permission scoping
adhook addresses promotions, posts, and subtenants by ID in the URL path, so you can pin the agent to one subtenant or one campaign, and you choose whether it may create and delete or only read. An agent can be limited to reporting on a single client's promotions.
Credential isolation
Your adhook 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 'schedule a social post' or 'create an ad promotion', and Jentic returns the matching adhook operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using adhook.io API through Jentic.
Why is there no official OpenAPI spec for adhook.io API?
adhook does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the adhook.io API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an adhook MCP server?
You don't need an MCP server to give your agent the adhook.io API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent schedules posts and manages promotions. No extra server runs in the agent's context.
Can I limit what my agent is allowed to do with the adhook.io API?
Yes. Because promotions, posts, and subtenants are addressed by ID in the URL path, you can pin the agent to a single subtenant or restrict it to read-only operations such as listing posts and reading statistics. It can then report on campaigns without creating or deleting them. Every call is logged.
What authentication does the adhook.io API use?
The adhook.io API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected when the agent makes a call, so it never appears in the agent's prompt or logs.
Can my agent manage multiple client accounts with the adhook.io API?
Yes. adhook models each client as a subtenant, so an agent can list subtenants, then schedule posts and run promotions scoped to one client at a time, which suits agencies managing many brands.
What are the rate limits for the adhook.io API?
The OpenAPI spec does not specify rate limits. Check the adhook documentation for the current limits before scaling an agent's throughput.
How does my agent schedule a post through Jentic?
Search Jentic for 'schedule a social post' and it returns the adhook.io create-post operation with its input schema. Store your bearer token once, then the agent supplies the content and channels and adhook queues the post.
GET STARTED