Ahrefs API

Name: Ahrefs API
Brand: Ahrefs API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingSeo Sembearer31 EndpointsREST

For Agents

Pull SEO research data from Ahrefs - backlinks, referring domains, organic and paid keywords, keyword volume, SERP overview, and subscription usage - through 31 GET endpoints.

Install Jentic One Beta

Connect the Ahrefs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ahrefs 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.

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 | sh

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 instance

Jentic 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 Ahrefs API.

Retrieve domain rating, backlink stats, and outlink stats for any domain

Pull historic time series for domain rating, URL rating, refdomains, and metrics

List backlinks, referring domains, anchors, and broken backlinks for a target

GET STARTED

Start building with Ahrefs API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Ahrefs API for, with concrete tasks.

★ Backlink Profile Analysis

SEO teams pull backlinks, referring domains, and anchor distribution for a target via Site Explorer endpoints. /v3/site-explorer/backlinks returns the link list with attributes like rating and anchor text, while /v3/site-explorer/refdomains aggregates by domain. Combined with the historic endpoints, an integration can chart link growth or detect drops over time.

GET /v3/site-explorer/backlinks?target=example.com&limit=100 and tabulate by ahrefs_rank

Keyword Research Automation

Content and growth teams run keyword overview and ideas calls to size opportunity at scale. /v3/keywords-explorer/keyword-overview returns volume, difficulty, and CPC for one or many seeds, while /v3/keywords-explorer/keyword-ideas expands a seed into a full idea list. The volume-by-country endpoint helps with international planning without per-region clicking.

GET /v3/keywords-explorer/keyword-overview?keywords=electric%20bikes&country=us

Organic Performance Tracking

Marketing teams sync Ahrefs organic data into their own dashboards. /v3/site-explorer/all-organic-keywords lists ranking keywords for a domain, /v3/site-explorer/top-pages returns the highest-traffic pages, and /v3/site-explorer/organic-competitors surfaces overlapping rivals. With history endpoints, the same agent can report trend lines without re-querying the slow paths.

GET /v3/site-explorer/top-pages?target=example.com&country=us&limit=50

Quota-Aware Batch Research

Ahrefs charges row credits, so sustained automation needs to budget queries. The Subscription endpoints expose remaining row credits, letting an agent check capacity before kicking off a wide research run. Batch Analysis offers higher throughput for repeated lookups against the same metric across many targets.

GET the subscription info endpoint to read remaining_rows before running a batch analysis

AI Agent SEO Research via Jentic

An agent built on Jentic can answer natural language SEO questions - 'compare backlinks growth between us and competitor X this quarter' - by chaining Site Explorer history calls. Jentic stores the bearer token in its vault and applies it on each call, so the agent never sees the raw API key while still benefiting from the read-heavy GET-based design.

Use Jentic to search 'get a domain rating from Ahrefs', execute the call, then chain into backlinks-stats

Key Endpoints

31 endpoints — jentic publishes the only available openapi specification for ahrefs api v3, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v3/site-explorer/domain-rating

Get domain rating

GET

/v3/site-explorer/backlinks

List backlinks for a target

GET

/v3/site-explorer/refdomains

List referring domains

GET

/v3/site-explorer/all-organic-keywords

List organic keywords for a target

GET

/v3/site-explorer/top-pages

List top pages by traffic

GET

/v3/keywords-explorer/keyword-overview

Get keyword overview metrics

GET

/v3/keywords-explorer/keyword-ideas

Generate keyword ideas

GET

/v3/site-explorer/broken-backlinks

List broken backlinks

GET

/v3/site-explorer/domain-rating

Get domain rating

GET

/v3/site-explorer/backlinks

List backlinks for a target

GET

/v3/site-explorer/refdomains

List referring domains

GET

/v3/site-explorer/all-organic-keywords

List organic keywords for a target

GET

/v3/site-explorer/top-pages

List top pages by traffic

Why Jentic?

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

Credential isolation

Your Ahrefs bearer token is stored once, encrypted, by your own Jentic One instance and attached at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get backlinks for a domain', and Jentic returns the matching Ahrefs operation with its query parameters, including target, country, mode, and limit, so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Ahrefs API through Jentic.

Why is there no official OpenAPI spec for Ahrefs API?

Ahrefs publishes API documentation but not an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Ahrefs API 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 Ahrefs API use?

The API uses a bearer token in the Authorization header. Tokens are issued from your Ahrefs API plan. Through Jentic, the token is held in the credential vault and injected at execution time, so the secret never appears in agent context.

How do I get backlinks for a domain through the Ahrefs API?

Call GET /v3/site-explorer/backlinks with target set to the domain and optional filters such as mode, history, and limit. The endpoint returns paginated backlink rows including referring page, anchor, and link strength metrics.

How are Ahrefs API row credits consumed?

Each row in a response counts against your plan's monthly row credits. Use GET subscription info to read remaining_rows before batch jobs and prefer aggregated endpoints (refdomains, anchors) over raw backlink listings when you only need totals.

How do I run keyword research through Jentic?

Search Jentic for 'run an Ahrefs keyword overview'. Load the GET /v3/keywords-explorer/keyword-overview schema, supply seed keywords and a country, and execute. Jentic adds the bearer token, returns the volume, difficulty, and CPC fields.

Can I get historic data for a domain rating?

Yes. GET /v3/site-explorer/domain-rating-history returns a time series of domain rating values for a target, useful for trend analysis without storing historical snapshots yourself.

Can I limit what my agent is allowed to do with the Ahrefs API?

Yes. Every Ahrefs operation is a read, so with your self-hosted Jentic One instance you decide which of those reads your agent may call, and your own rules define the allowed set. You can, for example, let it fetch domain rating and backlinks while leaving keyword overview, keyword ideas, or the subscription endpoints out, and anything you exclude stays unreachable. Because Ahrefs takes target, country, mode, and limit as query parameters on GET calls, the agent can only run the read operations you permit.