canonical: https://jentic.com/apis/adhook.io/adhook-main # adhook.io API Jentic publishes the only available OpenAPI specification for adhook.io API, keeping it validated and agent-ready. The adhook.io main API exposes 139 endpoints for managing real-estate listings, paid promotions across Facebook, Google, and LinkedIn, influencer collaborations, and cross-channel campaign statistics. Use it to publish listings as ads, retrieve placement and post-level metrics, and manage subtenants and targeting templates from one integration. Authentication is by API key passed in the Authorization header. ## For AI agents Manage adhook.io listings, paid ad promotions across Facebook, Google, and LinkedIn, influencer posts, and cross-channel campaign statistics through a single API. ## Scope Does not handle email marketing, organic social posting, or CRM contact management - use for paid ad publishing and reporting across Facebook, Google, and LinkedIn only. ## Capabilities - Publish real-estate listings as paid ads on Facebook, Google, and LinkedIn from one workflow - Retrieve ad, channel, placement, post, and target statistics across networks for unified reporting - Manage influencer posts and approval state for content tied to specific listings - Configure reusable targeting templates that can be applied to many promotions - Register FCM device tokens for push notifications about campaign and listing events - Manage subtenants and tags to organise multiple client accounts in agency setups ## Use cases ### Unified Real-Estate Advertising Workflow Property portals and estate agents can publish a single listing as a paid ad across Facebook, Google, and LinkedIn through the adhook.io main API rather than integrating each ad network separately. The API handles channel-specific differences in creative format and targeting, so a listing launched once is fanned out to all configured channels in minutes. Example prompt: Create a new listing, upload three images, and start a promotion targeting Berlin renters across Facebook and Google with a 14-day budget cap ### Cross-Channel Performance Reporting Marketing teams pull normalised ad performance data from one source rather than maintaining separate Facebook, Google Ads, and LinkedIn integrations. The Statistic endpoints expose ad, channel, placement, post, and target breakdowns so dashboards roll up a complete picture of paid spend without per-channel reconciliation work. Example prompt: Pull placement statistics for the last 7 days for all promotions under subtenant 22 and group results by channel ### Influencer Content Approval Agencies running influencer collaborations against listings can list, review, edit, and approve influencer posts through the Influencers endpoints. The full content review workflow is API-driven so agents and automation can replace manual UI review for routine approvals. Example prompt: List pending posts for influencer 312, then approve any with engagement above 3 percent via PUT /v1/influencers/{id}/posts/{postId} ### Agent-Driven Campaign Operations via Jentic AI agents can search for adhook operations by intent through Jentic, load only the schema they need, and execute campaign updates without traversing 139 endpoint specifications. The API key is held in your Jentic One instance and never enters the agent's prompt context, which matters because the key authorises spend on subtenant ad budgets. Example prompt: Search Jentic for 'pause adhook listing', load PUT /v1/listings/{id}/status, and execute it for listing 9931 ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /v1/listings | List real-estate listings | | PUT | /v1/listings/{id}/status | Change a listing's status | | POST | /v1/listings/{id}/images | Upload images for a listing | | GET | /v1/influencers | List influencers | | PUT | /v1/influencers/{id}/posts/{postId} | Update an influencer's post | | POST | /v1/customEvents | Create a custom tracked event | ## Key resources - **Listings** — Manage real-estate listing records, statuses, and uploaded images - **Promotions** — Run paid promotions across Facebook, Google, and LinkedIn - **Statistics** — Retrieve ad, channel, placement, post, and target performance data - **Influencers** — List influencers and review posts tied to listings - **Targeting Templates** — Build and reuse audience targeting definitions - **Subtenants** — Manage subtenant accounts for agency configurations - **Custom Events** — Register tracked events against advertising strategies - **Notifications** — Read and acknowledge in-platform notifications ## Why Jentic - **Setup:** Wiring adhook.io by hand means handling its API key auth and mapping calls across Facebook, Google, and LinkedIn ad accounts yourself. Through Jentic you install once, import adhook.io from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** adhook.io puts the listing and influencer id in the URL path (/v1/listings/{id}/...), so a rule can pin your agent to one listing: it can read and update status for that listing and nothing else. You choose the operations it may call, so a status change stays available only if you include it. - **Credential handling:** Your adhook.io API key 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 an adhook listing promotion' or 'update a listing status', and Jentic returns the matching adhook.io 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 the Facebook ad account and pages adhook.io publishes to. - **LinkedIn API** — LinkedIn's native API for sponsored content and ad management. - **Mailchimp API** — Marketing platform combining email and multi-channel ad audiences. ## FAQ ### Why is there no official OpenAPI spec for adhook.io API? Adhook GmbH does not publish a standalone OpenAPI specification for its main API. Jentic generates and maintains this spec from adhook.io's live documentation 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 adhook.io API use? The adhook.io main API uses API-key authentication. The key is supplied in the Authorization header on every request. Through Jentic, the key is stored encrypted in the vault and injected at execution time so the agent never receives the raw secret. ### Can I publish a listing to multiple ad channels with the adhook.io API? Yes. A listing managed through /v1/listings can be promoted on Facebook, Google, and LinkedIn from the same record. The Promotion and Statistic tags expose endpoints for launching and reporting on those campaigns without integrating each network separately. ### How do I retrieve placement statistics with the adhook.io API through Jentic? Search Jentic for 'adhook placement statistics', load the matching Statistic - Placement endpoint, and execute it with your placement ID and date range. Jentic returns the input schema so the agent supplies only the parameters the endpoint accepts. ### What are the rate limits for the adhook.io API? The OpenAPI spec does not publish numeric rate limits. Adhook applies fair-use limits server-side; if you receive HTTP 429 responses, back off and retry. Through Jentic, retry behaviour can be set in the execution request rather than coded by hand. ### Can I manage influencer posts programmatically with the adhook.io API? Yes. Endpoints under the Influencers area let you list influencers (GET /v1/influencers), retrieve their posts (GET /v1/influencers/{id}/posts), and update individual posts (PUT /v1/influencers/{id}/posts/{postId}). This replaces manual UI review for routine approvals. ### Can I limit what my agent is allowed to do with the adhook.io API? Yes. Because you run Jentic One yourself, your own rules decide which adhook.io operations and which stored API key the agent may use. Since adhook.io puts the listing and influencer id in the URL path, such as /v1/listings/{id}/status, you can pin the agent to a single listing so it only reads and updates the status of that one record. You choose the operations it may call, so a promotion launch or a status change is available only if you explicitly include it.