$100 free credit on sign-up, then $0.10 per 1,000 calls

Buyer's questions

Ahrefs Backlinks Integration or Per-Call Pricing for Your Tool

If you resell or embed link metrics, the pricing model matters more than the logo. Here is the decision laid out as questions, with the cost sums we can verify.

Isometric balance scale comparing a complex gear against a simple silver coin

Decide by answering four questions

  • Do you need keywords or rank tracking?

    Then Ahrefs or Semrush is the fuller product and you should buy it. Our API holds link data only.

  • Is your volume spiky?

    Prepaid credit costs nothing in a quiet month. A plan with monthly units bills the same whether you import or not.

  • How many rows per request?

    Ahrefs charges at least 50 units per request. We bill one call once, whatever the number of rows up to 1,000.

  • How fresh must it be?

    Our index refreshes about monthly. Daily-fresh crawl data is an Ahrefs strength.

The sums we can check

Ahrefs figures as published on its pricing and API pages at the time of writing; verify before you buy.
ItemAhrefs API unitsLinkfluence credits
Entry priceFrom $129 a month for 200,000 units$0.10 per 1,000 calls, no monthly minimum
Minimum cost of one requestAt least 50 units1 to 3 credits, $0.0001 each
Pull of 1,000 rowsUnits per request, 50 at minimumOne call, 2 credits for refdomains
Starting balancePlan dependent$100 free credit on sign-up
Keyword dataYesNo
Workshop bench with a wide net for stones and a magnifying glass for a gem

Where each one sits in an outreach stack

Think of it as two jobs. One job is deciding who to pitch, which needs thousands of cheap authority checks. The other is proving results, which may need keywords and position history.

Many teams will end up with both: a per-call API inside the CRM for scoring, and a seat for whoever writes the reports. That is not a contradiction. It is the cheapest way to cover each job. The report layout page shows where each source fits, and the import recipe shows the cheap half.

A cost sketch for a mid-sized tool (hypothetical)

Suppose your platform onboards 200 new customers a month, each importing about 1,500 prospect domains. That is 300,000 domains, or 150 bulk_dr calls: 150 credits, $0.015.

Add a deeper pull on the best 10 percent, 30,000 domains at 2 credits, which is 60,000 credits or $6. The whole month lands near $6, with no minimum in a quiet month. These figures are an illustration, not a quote, and your mix will differ. Treat it as a sketch.

Position

Use ours for volume lookups, theirs for depth

If your integration is a column of authority scores and a shortlist view, per-call pricing wins on cost. If it needs search-ranking history or daily freshness, pay for the bigger tool.

  • No subscription for ours
  • Sign-in by Google, top-up in USDT (TRC-20)

Map the integration before you price it

An integration is not one job. It is a chain of calls, each with its own volume, freshness need and failure mode. Priced as a single line item, the chain hides the expensive link, so map it first.

Write the chain on one page: where the domains come from, which call runs on each, how often it runs and what happens on an error. An Ahrefs backlinks integration can look cheap on paper and still surprise you once every retry and every refresh is counted.

Where the volume really comes from

Most integrations do not call the API on a user click. They call it in bulk, after an import, or on a nightly schedule over the prospect table. That makes volume predictable, which helps under either pricing model.

Count the domains per import and the imports per month before you compare any price. That total is the figure the rest of this page turns into money.

What happens on the error path

A bad key returns 401 and an empty balance returns 402. Either response should stop the job rather than write blanks into the table. Plan the stop, the alert and the retry rule before the first customer uses the feature.

Every retry is one more call in your own count. Set a limit on retries and log how many happen, so a noisy night does not become a surprise invoice.

Who sees the number, and how it is labelled

If the integration shows link metrics to end users, the label matters as much as the value. A column called DR, sitting next to an Ahrefs DR column, invites a comparison that neither number can win.

Put the source in the column name and the formula in a tooltip or footnote. Then the reader knows what the number measures before they act on it.

A short line beside the number helps as well, for example a note that the score refreshes about monthly. Readers then know how old the figure can be before they ask.

Which results to keep, and for how long

A link count changes only when the index refreshes, so storing it again every day adds calls without adding information. Store the result with its fetch date, then reuse it until the next refresh cycle.

Keep the raw response for a short period, and keep the derived fields for as long as the product needs them. That split lets you answer a support question without paying for the same lookup twice.

Plan a per-call integration in four steps

01

Estimate the monthly calls

Multiply the expected imports by the number of chunks. A chunk of 2,000 domains is one bulk_dr call at 1 credit, and the import recipe shows the same split.

02

Choose the depth per row

Decide which rows get the 2-credit pulls, such as refdomains or anchors, and set a monthly cap on how many of them run.

03

Set the stop rules

Halt on 401 or 402, and write the _credits balance to the log after every batch so the cost is visible at any point.

04

Re-price after one real month

Compare the actual credit total with your estimate, then adjust the caps before you scale the feature to more customers.

Isometric landscape with lush and sparse gardens connected by an irrigation pipe

How the two pricing models behave at different sizes

The right model depends less on the price list than on the shape of your traffic. Two rough pictures show the difference, and both are illustrations you can change to match your own numbers.

Look at the quiet months as closely as the busy ones. A plan that charges the same in both is only cheap if you use it heavily.

A single example rarely settles the choice. Run your own estimate with the same steps, and let the result decide, not the first impression of either price.

A small team with one import a week

Say a small team imports one list a week, with 800 domains each. That is one bulk_dr call per list, so about four calls a month. At one credit each that is four credits, or $0.0004 at the per-credit price.

Prepaid credit suits that pattern. Nothing is charged while the team is quiet, and the balance waits until it is spent. A monthly unit plan would bill the same amount whether the team imported anything or not.

A platform with many customers

Now say the platform onboards many customers, each importing about 1,500 domains. Volume becomes the main driver, and the deeper pulls become the larger share of the bill.

Keep those deeper pulls behind a threshold and a monthly cap, so the expensive calls run only on rows that matter. That single rule usually decides whether the bill stays predictable as the customer count grows.

Support load grows as well. When a customer asks why a number moved, the answer should already sit in the log, with the batch, the date and the cap that applied. A log built for that question takes little time to keep and saves a long run of replies later.

When a reseller needs fixed margins

A reseller who sells link metrics at a fixed monthly fee needs a cost that does not wander. Per-call pricing can wander, because a busy customer can double the calls in a week.

The answer is a cap per account, written into the product rules. With a cap in place, the margin is calculable, and the variable cost becomes a line you can plan for rather than a risk you hope will stay small.

Integration questions

Can I use both Ahrefs and this API in one tool?

Yes, nothing prevents it. Keep the sources in separate columns, label each one, and never average a Linkfluence DR with an Ahrefs DR. They use different formulas, so mixing them hides real differences.

Is there a rate limit I should plan for?

Plan for cost rather than speed: you are billed per call, so batch with bulk_dr and cache results. Handle 401 and 402 responses in the job so a bad key or empty balance fails loudly.

Does CORS allow browser calls?

CORS is open, so browser calls work. Yet a key in front-end code is visible to anyone, so route calls through your server and keep the free domain action for public widgets.

Which response data can I rely on?

Every response includes ok, and authenticated ones add _credits with the cost and the balance. Check ok before you write anything to your table.

Should results be cached between imports?

Usually yes. Store each score with its fetch date and reuse it until the next index refresh. Re-calling the same domain inside one refresh cycle costs credit and returns the same numbers, so the cache pays for itself quickly.