adhook.io API

Name: adhook.io API API
Brand: adhook.io API
Availability: InStock

★ Only Publicly Available SpecMarketingAdvertisingbearer138 EndpointsREST

For Agents

Create and manage paid advertising campaigns across Facebook, Google, and LinkedIn through adhook.io, retrieve cross-channel performance statistics, and manage influencer posts and listings.

Quickstart

Get started with adhook.io API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"publish a real-estate listing as a paid ad"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with adhook.io API API.

Publish real-estate listings as paid ads on Facebook, Google, and LinkedIn from a single workflow

Retrieve ad, channel, placement, and post statistics for cross-platform campaign reporting

Manage influencer posts and approve or reject influencer-generated content tied to a listing

Configure targeting templates and reuse audience definitions across multiple promotions

GET STARTED

Start building with adhook.io API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for adhook.io API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for adhook.io API, keeping it validated and agent-ready. The adhook.io API powers a multi-channel advertising platform for managing real-estate and influencer campaigns across Facebook, Google, and LinkedIn from a single account. It exposes 138 endpoints covering listings, posts, promotions, statistics, targeting templates, and influencer collaboration. Use it to publish listings as paid ads, retrieve campaign and placement statistics, and manage subtenant accounts in agency setups.

Use Cases

Patterns agents use adhook.io API API for, with concrete tasks.

★ Multi-Channel Real-Estate Ad Distribution

Estate agents and listing portals can push a single property listing as paid ads across Facebook, Google, and LinkedIn through adhook.io, reusing targeting templates and creative assets. The API handles channel-specific listing uploads, image attachments, and status transitions so an agent does not need to call each ad platform directly. Typical setup runs in minutes per listing once a strategy and targeting template are in place.

Create a listing for property ID 4521, upload three images via POST /v1/listings/{id}/images, then promote it on Facebook and Google using an existing targeting template

Cross-Channel Campaign Reporting

Marketing analysts can pull aggregated statistics for ads, channels, placements, posts, and targets without scraping each ad platform's reporting UI. The Statistic endpoints return normalised metrics across Facebook, Google, and LinkedIn so a single dashboard or weekly report covers the full portfolio. This removes the need to maintain separate connectors for each network.

Fetch ad-level statistics for the last 7 days for subtenant 88 and roll up impressions, clicks, and spend by channel

Influencer Post Coordination

Agencies running influencer collaborations on behalf of property listings can list, review, and update influencer posts tied to specific listings through the Influencers endpoints. Posts can be approved, rejected, or edited via PUT /v1/influencers/{id}/posts/{postId} so the workflow is fully programmatic rather than manual review in a UI.

List all pending posts for influencer 312, then approve posts whose engagement rate is above 3 percent

Agent-Driven Campaign Operations via Jentic

AI agents built on Jentic can search for adhook operations by intent, load the input schema for the matching endpoint, and execute campaign updates without having to read 138 endpoint specifications up front. Bearer token authentication is handled by the Jentic vault so the agent never sees raw API keys, which is important because adhook.io tokens grant access to subtenant ad budgets.

Search Jentic for 'pause adhook listing', load the input schema for PUT /v1/listings/{id}/status, and execute it for listing 9931 with status paused

Key Endpoints

138 endpoints — jentic publishes the only available openapi specification for adhook.

METHOD

PATH

DESCRIPTION

GET

/v1/listings

List all real-estate listings

PUT

/v1/listings/{id}/status

Change a listing's status

POST

/v1/listings/{id}/images

Upload images for a listing

POST

/v1/customEvents

Create a custom tracking event

GET

/v1/influencers

List all influencers

GET

/v1/notifications/count

Get unread notification count

GET

/v1/listings

List all real-estate listings

PUT

/v1/listings/{id}/status

Change a listing's status

POST

/v1/listings/{id}/images

Upload images for a listing

POST

/v1/customEvents

Create a custom tracking event

GET

/v1/influencers

List all influencers

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

adhook.io bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access — raw tokens never enter the agent's context, which matters because these tokens grant access to subtenant ad budgets.

Intent-based discovery

Agents search Jentic by intent (e.g., 'publish a listing as a Facebook ad') and Jentic returns the matching adhook operation with its input schema. The agent does not need to read all 138 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.

Complementary

Facebook Graph API

Direct access to Facebook ad accounts, pages, and posts that adhook.io publishes to.

Choose Facebook Graph API when you need lower-level access to a single Facebook ad account or page; use adhook.io when you want a unified workflow across Facebook, Google, and LinkedIn.

Complementary

LinkedIn API

LinkedIn's native API for sponsored content and ad management.

Use the LinkedIn API directly when you only target LinkedIn and need granular sponsored content control; use adhook.io when LinkedIn is one of several channels.

Alternative

Mailchimp API

Marketing platform with audience management and ad integrations across multiple channels.

Choose Mailchimp when the workflow is email-led with ad retargeting as a secondary channel; choose adhook.io when paid social and search ads are the primary deliverable.

FAQs

Specific to using adhook.io API API through Jentic.

Why is there no official OpenAPI spec for adhook.io API?

Adhook GmbH does not publish a standalone OpenAPI specification. Jentic generates and maintains this spec from the live adhook.io API 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 API uses HTTP bearer authentication. Every request must include an Authorization header with a bearer token issued by adhook.io. Through Jentic, this token is stored encrypted in the vault and injected at execution time so the agent never sees the raw secret.

Can I publish a listing to multiple ad channels with the adhook.io API?

Yes. Listings managed via /v1/listings can be promoted on Facebook, Google, and LinkedIn through the Promotion and Statistic endpoints. A single listing record drives ads across all three channels rather than requiring you to call each ad platform's API directly.

How do I retrieve campaign performance with the adhook.io API through Jentic?

Search Jentic for 'adhook campaign statistics', load the relevant Statistic endpoint (Statistic - Ad, Statistic - Channel, Statistic - Placement, or Statistic - Post), and execute with your subtenant or listing ID. Jentic returns the input schema so the agent supplies only the parameters that endpoint actually accepts.

What are the rate limits for the adhook.io API?

The OpenAPI specification does not publish rate limits. Adhook applies fair-use limits behind the scenes; if you receive HTTP 429 responses, back off and retry with exponential delay. Through Jentic, retries can be configured in the execution request rather than coded by hand.

Can I manage influencer posts programmatically with the adhook.io API?

Yes. The Influencers tag groups endpoints for listing influencers (GET /v1/influencers), retrieving their posts (GET /v1/influencers/{id}/posts), and updating individual posts (PUT /v1/influencers/{id}/posts/{postId}). This covers the full review-and-approve workflow without using the adhook UI.