adhook.io API
Browse all Adhook APIs★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingapiKey139 EndpointsREST
For Agents
Manage adhook.io listings, paid ad promotions across Facebook, Google, and LinkedIn, influencer posts, and cross-channel campaign statistics through a single API.
Use for: I want to launch a Facebook and Google ad campaign for a real-estate listing, Retrieve the statistics for placement 442 over the last 30 days, List all influencer posts attached to listing 9931, Update the status of a listing to paused
Not supported: 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.
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.
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://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 adhook.io API.
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
Patterns agents use adhook.io API for, with concrete tasks.
★ 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.
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.
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.
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 the Jentic vault and never enters the agent's prompt context, which matters because the key authorises spend on subtenant ad budgets.
Search Jentic for 'pause adhook listing', load PUT /v1/listings/{id}/status, and execute it for listing 9931
Key Endpoints
139 endpoints — jentic publishes the only available openapi specification for adhook.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
adhook.io API keys are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw key never enters the agent's context, which matters because the key authorises spend across Facebook, Google, and LinkedIn ad accounts.
Intent-based discovery
Agents search by intent (e.g., 'launch an adhook listing promotion') and Jentic returns the matching operation with its input schema. The agent does not need to scan 139 endpoint definitions to find the right call.
Time to first call
Direct adhook.io integration: 1-3 days for auth, error handling, and channel-specific edge cases. Through Jentic: under 30 minutes — search, load schema, execute.
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 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 at https://app.jentic.com/sign-up.
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.
GET STARTED