canonical: https://jentic.com/apis/adhook.io/adhook # adhook.io API 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. ## For AI 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. ## Scope Does not handle ad-creative design, payment processing, or website analytics. Use for social publishing and ad-campaign management only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: List every active promotion under the subtenant for client Acme and report total spend ## Key endpoints | 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 | ## Key resources - **Posts** — Scheduled and published social content with calendars, counts, and statistics - **Promotions** — Paid advertising campaigns with budgets, targeting, and calendars - **Subtenants** — Client accounts for agency-style multi-brand management - **Targeting templates** — Reusable audience definitions applied across promotions ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **Buffer** — Buffer schedules and publishes social posts without adhook's paid-promotion tooling. - **NativeAds** — NativeAds places native advertising that complements adhook's social promotions. - **LinkedIn** — LinkedIn adds professional-network reach to campaigns managed in adhook. ## FAQ ### 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.