How Jentic Works
From API assessment to production deployment in four simple steps.
PLATFORM
CAPABILITIES
TOOLS
GET STARTED
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.
Jentic publishes the only available OpenAPI specification for 4Dem, keeping it validated and agent-ready. 4Dem is an Italian email marketing and marketing automation platform with 208 endpoints covering recipients, address books, campaigns, content, senders, reports, workflows, suppressions, custom fields, consents, SMS, e-commerce stores, and webhooks. Authentication uses HTTP bearer tokens obtained from the /authenticate endpoint and refreshed via /refresh_token. The API is suitable for managing the full lifecycle of an email programme from list management through send to performance reporting.
Jentic publishes the only available OpenAPI specification for 5 Stars Reputation API, keeping it validated and agent-ready. The 5 Stars Reputation API is the integration interface for the 5 Stars Reputation review and reputation management platform, exposing three POST endpoints that register customer locations, push existing reviews into a 5 Stars Reputation account, and import contacts that should be invited to leave a review. The API is intended for businesses syncing point-of-sale or CRM data so that 5 Stars Reputation can run review-request campaigns automatically. Authentication uses an API key supplied in the request body or header.
Jentic publishes the only available OpenAPI specification for 7Targets API, keeping it validated and agent-ready. The 7Targets API is the integration interface for 7Targets, an AI sales assistant that automates lead nurturing and follow-up email sequences. The four endpoints cover lead creation and updates, stopping follow-up sequences, and assigning leads to specific AI assistants inside an account. Sales and marketing teams use it to push new leads from forms or CRMs into the 7Targets nurture engine without manual entry. Authentication uses a bearer token issued in the 7Targets account settings.
Jentic publishes the only available OpenAPI specification for AB.GL API, keeping it validated and agent-ready. AB.GL is a link management and URL shortening service with a small REST surface for creating and listing short links and deleting them when they are no longer needed. The four endpoints cover list, create, retrieve, and delete on the /links resource, gated by a single API-key header. It is suited to teams that want shortened tracking links without taking on a heavier marketing automation stack.
Jentic publishes the only available OpenAPI specification for Action Network API, keeping it validated and agent-ready. Action Network is a progressive organising platform built on the OSDI standard, exposing endpoints to manage people, petitions, events, fundraising pages, forms, tags, and broadcast messages. The API uses a per-group OSDI-API-Token header for authentication and follows hypermedia conventions, with collections under /api/v2/. The spec covers 52 operations across nine resource groups including campaigns, wrappers, and messages.
Jentic publishes the only available OpenAPI specification for ActiveTrail API, keeping it validated and agent-ready. ActiveTrail is an email marketing and automation platform with endpoints for contacts, groups, email campaigns, SMS campaigns, and automations. The spec covers 20 operations under five tags — Contacts, Groups, Campaigns, Automations, and SMS — with the API key passed in the Authorization header. The base URL points at ActiveTrail's MyMarketing platform.
The Ad Exchange Buyer API II lets Authorized Buyers programmatically manage their accounts on Google's Ad Exchange. It covers client and invitation management, real-time bidding configurations including pretargeting and creatives, auction packages, marketplace programmatic deals (proposals, products, deals, finalized deals), and bidder-level filtering and bid metric reports. Buyers and demand-side platforms use it to provision client buyers, run experiments, troubleshoot bid filtering, and negotiate deals with publishers without using the Authorized Buyers UI.
The Ad Experience Report API exposes Google's findings on sites that show ads violating the Better Ads Standards — interruptions like full-page interstitials, auto-playing video with sound, and prestitial countdown ads. It returns the ad-experience status (Failing, Passing, or Not Reviewed) for a single site and a list of all sites currently failing the report. Publishers and ad-quality teams use it to monitor whether their domains are at risk of having Chrome filter ads on them.
The Adform Seller Campaigns API lets sell-side ad operations teams manage direct-sold campaigns and their line items inside the Adform supply-side platform. The five endpoints cover listing, creating, updating, and deleting campaigns at /, plus retrieving a single campaign at /{id}. It is the programmatic equivalent of the Adform UI's Seller Campaigns module, intended for publishers automating booking ingestion from order management systems. Useful when a publisher wants to bridge a CRM-style booking tool with the Adform stack without manual data entry.
Jentic publishes the only available OpenAPI specification for Adgogo Open API, keeping it validated and agent-ready. Adgogo (also branded Quickeast) is a digital advertising operations platform popular with APAC marketers running paid social and search campaigns. The Open API has three POST endpoints — ad list, leads list, and report — designed for periodic pulls into a customer's BI warehouse or CRM rather than real-time creative editing. Authentication is an AccessKey passed in the AccessKey header.
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.
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.
Jentic publishes the only available OpenAPI specification for the Admanage AI Ad Management API, keeping it validated and agent-ready. The Admanage AI API exposes 61 endpoints for launching, duplicating, renaming, and reporting on ads across Facebook, TikTok, Snapchat, Pinterest, Google Ads, AppLovin/Axon, and Taboola from a single integration. It also covers media library management, drafts, and automation rules. Use it to consolidate ad operations for performance teams running campaigns on multiple networks at once.
The AdMob API lets mobile app publishers programmatically read account, app, ad unit, and reporting data from their AdMob account. It exposes endpoints to list AdMob accounts the caller has access to, enumerate apps and ad units under each account, and generate network and mediation reports against custom date ranges and dimensions. App publishers and analytics teams use it to feed AdMob earnings into BI dashboards, monitor ad-unit fill rate, and produce reconciliation reports without scraping the AdMob UI.
Adobe Experience Manager (AEM) is Adobe's enterprise content management system used to author, manage, and publish digital experiences. This OpenAPI specification, maintained by Shine Solutions, exposes 48 endpoints for AEM administrative and content operations including OSGi configuration management, package management, replication agents, user and group administration, and JCR node operations. Use it to script AEM environment setup, configuration, and content lifecycle tasks. Authentication is HTTP basic against an AEM instance.
The AdSense Host API gives AdSense host partners programmatic access to publisher onboarding workflows, ad code generation, and reporting on host-managed publisher accounts. It is intended for platforms that embed AdSense for content into their own products and need to associate end-publisher accounts. The interface is narrow by design and centres on starting and verifying association sessions between the host and a publisher's AdSense account.
The AdSense Management API lets web publishers programmatically read their AdSense inventory and earnings. It exposes operations to enumerate accounts, ad clients, ad units, custom channels, URL channels, sites, payments, alerts, and saved reports, and to generate ad-hoc earnings and performance reports against custom date ranges, dimensions, and metrics. Publishers and analytics teams use it to feed AdSense data into BI dashboards, monitor channel performance, and produce reconciliation reports without scraping the AdSense UI.
The 'Advertising' integration focuses on allowing 3rd party systems and customized websites to sync available properties from Palace to display up-to-date advertising on a company's website.<BR><BR><BR>The 'Advertising Integration' area does NOT require an upgrade from a 'Standard' API account to a 'Premium' API Account. There is a NO cost involved in using these contracts unless you are a 3rd Par. The API exposes 5 endpoints.
Jentic publishes the only available OpenAPI specification for Agility CMS REST API, keeping it validated and agent-ready. Agility CMS is a headless content management system that lets agents and applications fetch published content, preview staging content, and synchronise large catalogues of pages, lists, and galleries from a content instance. The API exposes 15 read endpoints scoped by instance GUID, API type (fetch or preview), and locale, covering single items, lists by reference name, sitemaps, paginated sync feeds, URL redirections, and content models. Authentication uses an APIKey header, and responses return structured JSON ready for downstream agent reasoning or static site rendering.
Jentic publishes the only available OpenAPI specification for Agillic API, keeping it validated and agent-ready. Agillic is a customer marketing automation platform for managing recipients, segmenting audiences, and orchestrating cross-channel campaigns through flows. The API exposes 81 endpoints covering recipient CRUD, batch upserts, one-to-many tables, event achievement, target group membership, flow execution, app push device registration, asset management, and asynchronous data exports. Authentication supports OAuth2 bearer tokens (preferred) and HTTP basic for legacy clients.
Jentic publishes the only available OpenAPI specification for the agillic.net surface of Agillic API, keeping it validated and agent-ready. This is the bearer-only slice of the Agillic marketing automation platform, exposing 37 endpoints for managing recipients, one-to-many tables, global data, app push registration, target groups, flow execution, asset uploads, and asynchronous data exports. It is intended for integrations that need a focused subset of the platform without OAuth2 setup, while still authenticating against the same EU1 host.
Jentic publishes the only available OpenAPI specification for Ahrefs API v3, keeping it validated and agent-ready. Ahrefs is an SEO data platform; the v3 API exposes 31 read endpoints across Site Explorer (backlinks, referring domains, organic traffic), Keywords Explorer (keyword overview, ideas, volume history), SERP Overview, Subscription metadata, and Batch Analysis. Authentication uses a bearer token, and every endpoint is a GET designed for read-heavy SEO research workflows.
Jentic publishes the only available OpenAPI specification for Aimfox API, keeping it validated and agent-ready. Aimfox (formerly LinkedApe) is a LinkedIn outreach automation platform exposing nine endpoints for managing campaigns, leads, messages, and connections. Agents can create and update LinkedIn outreach campaigns, list and inspect leads, send personalized messages, and inspect connection records. Authentication uses an API key supplied in the X-API-Key header issued from the Aimfox dashboard.
Jentic publishes the only available OpenAPI specification for Aimtell API, keeping it validated and agent-ready. Aimtell is a browser push notification platform for re-engaging website visitors with targeted messages across desktop and mobile web. The API exposes 46 endpoints covering manual, RSS, event-triggered, and welcome campaigns, subscriber and segment management, multi-site analytics, tracking pixels, and notification logs. Authentication uses an X-Authorization API key header, and operations are scoped per website.
Jentic publishes the only available OpenAPI specification for AirGift API, keeping it validated and agent-ready. AirGift is a digital gifting and rewards platform for sending branded gifts as part of marketing, sales, and customer success workflows. The API is intentionally minimal — two endpoints cover sending a digital gift and retrieving its status. Authentication is via an API key passed in the Authorization header.
Annex Cloud API v3.0 for loyalty program management including users, orders, points, rewards, segments, and campaigns. The API exposes 14 endpoints secured with apiKey, bearer authentication.
REST API for managing loyalty program users, orders, points, rewards, segments, and campaigns in Annex Cloud. The API exposes 14 endpoints secured with bearer authentication.
Jentic publishes the only available OpenAPI specification for Antavo Loyalty Engine API, keeping it validated and agent-ready. Antavo is a loyalty-program engine that exposes 18 REST endpoints covering customer profiles, point-earning and point-spending activities, reward claiming, custom-event ingestion, and entity records that drive program rules. The API is structured around the events and customers resources so agents can post earn/spend activities, retrieve a customer's transaction history, and trigger reward claims directly from a CRM or e-commerce flow. Authentication supports both an api_key query parameter and HTTP bearer tokens.
AppConnect V3 is a Constant Contact-aligned contacts and lists API exposing a small surface for syncing email subscribers and segment lists. The 10 endpoints cover contact CRUD on /contacts and list CRUD on /lists, with authentication via an Authorization header or x-api-key header. The API targets developers who need to push subscribers from a product backend into Constant Contact-style email marketing without integrating the wider Constant Contact platform.
Jentic publishes the only available OpenAPI specification for AppConnect V3, keeping it validated and agent-ready. The Constant Contact V3 API lets developers build integrations with the small-business email marketing platform, covering contacts, contact lists and tags, custom fields, segments, email campaigns and A/B tests, scheduling, reporting, events, and partner webhooks. Authentication uses OAuth 2.0 with scoped permissions for contact and campaign data alongside an x-api-key header for partner identification. The 116 endpoints span 17 resource groups and support both interactive contact management and bulk activities such as contact imports, list membership changes, and tagging operations.
Jentic publishes the only available OpenAPI specification for AppConnect V3, keeping it validated and agent-ready. AppConnect V3 is Constant Contact's contact and contact-list management API, exposing CRUD on contacts and contact lists for marketing email programs. Authentication uses an x-api-key header alongside an OAuth 2.0-style Authorization header. The endpoints cover listing, retrieving, creating, updating, and deleting both contacts and lists.
Jentic publishes the only available OpenAPI specification for Aprimo API, keeping it validated and agent-ready. Aprimo is a digital asset management and marketing operations platform used by enterprise marketing teams to store, organise, and distribute brand assets. The API exposes token-based authentication and resource retrieval so agents can fetch metadata and asset records from an Aprimo tenant. The current spec covers core access patterns: obtaining an access token, listing resources, and fetching individual resource details by ID.