Skip to content
SEOBlogBotSign up

DR lookups are free

Backlink checker API for developers who publish by script

Put a link check between your draft and your publish button. One HTTP call returns referring domains, anchors and a 0-100 rating as JSON, and DR lookups cost nothing.

Get $100 freeOpen the QA gate guide
  • Free: domain, overview, stats, suggest
  • 1 credit = $0.0001, no subscription
  • Bearer header or ?key= in the URL
GET /api.php?action=domainJSON

$ curl "https://seoblogbot.com/api.php?action=overview&q=nytimes.com&key=sk_live_..."

What it is for

What a backlink checker API for developers does inside a publishing pipeline

Your posts go out from a repo, a CMS webhook or a cron job, and nobody is watching the dashboard at 6 a.m. A link check that runs by itself is the only kind that survives. Four jobs teams wire up first.

Gate the draft

Before a post is scheduled, rate every outside host it links to with one bulk_dr call. The decision tree says which results block the post.

Audit after publish

A scheduled job pulls refdomains for the new URL's site and writes the count to your log. The runbook shows the workflow file.

Sweep the archive

Run a whole back catalogue through two or three calls instead of two hundred. The worked example uses made-up numbers and says so.

Watch the bill

Every authenticated reply carries _credits. Log it per run and the cost table tells you what a post costs.

Where we fit

A link-data API, not a keyword suite

If your pipeline needs rank tracking, keyword volumes or a daily-fresh crawl, Ahrefs or Semrush are the fuller products. If it needs link data per call at a tiny price, this is the narrower and cheaper tool.

  • Our own crawler and our own link index, refreshed roughly monthly.
  • No subscription and no minimum request size.
  • Ahrefs sells API units inside plans from $129 a month; see the comparison.

The call your CI job will repeat

Free actions need no key. Paid ones take a Bearer header, which keeps the key out of access logs.

bash
# 1 credit for up to 2,000 domains
curl -H "Authorization: Bearer sk_live_..." \
  "https://seoblogbot.com/api.php?action=bulk_dr&domains=example.org,example.net"

# 2 credits, up to 1,000 rows
curl -H "Authorization: Bearer sk_live_..." \
  "https://seoblogbot.com/api.php?action=refdomains&q=example.com&per=100"
domains in our link graph
181,132,097
domain-to-domain links
2,774,625,913
backlinks indexed
798.5 billion
free credit on sign-up
$100

How it works

From zero to a working gate in an afternoon

01

Sign in and copy a key

Google sign-in only. The account starts with 1,000,000 credits and asks for no card.

02

Replay one free call

Run action=overview against a domain you know. It costs nothing, so test your parser as often as you like.

03

Add the gate to your build

Call bulk_dr on the outbound hosts of the draft and fail the job below your threshold.

04

Schedule the audit

Cron or a workflow file calls the paid pulls after publish. Log _credits so you see spend per run.

Who it is for

Reading a reply before your pipeline trusts it

Reading a reply is the step that is easiest to skip. Every response carries ok, and an authenticated one adds _credits with the cost and the balance left. Parse both first. A script that writes data from a failed reply fills your log with empty rows.

A reply can also be valid and still useless, such as an empty list for a domain you know has links. Compare the count with last month before you call the result good.

Check the status before the body

Treat HTTP 401 and 402 as two different stops. A 401 means the key is missing or wrong, so fix the secret. A 402 means the credit has run out, and retrying will not help until you top up. Both need a person, not a retry loop.

Keep the credit line

Log the _credits field from every authenticated call, with the date and the action name. Over a month that log answers the question most teams ask too late: which job spent the credit. Free actions do not bill, so they add nothing to that line.

Checklist

Before you trust the job unattended

  • The script handles HTTP 401 and 402 as separate cases.
  • Every call logs the _credits balance.
  • Thresholds come from your own sample of posts, not from another tool's DA or DR.
  • Scheduled runs treat monthly data as monthly: no alert on a week-to-week wobble.
  • A failed check blocks the post or alerts a person, never silently passes.

FAQ

Questions from people wiring this into a pipeline

What is a backlink checker API for developers and who needs one?

It is an HTTP endpoint that returns link data as JSON, so a script can read it. Teams that publish through git, a CMS webhook or a scheduler use it to check posts without opening a dashboard.

Is there a rate limit I should plan around?

We publish no requests-per-second figure, so pace loops defensively: a short wait between items and separate handling for 401 and 402. Batch endpoints like bulk_dr cut call counts sharply anyway.

How much does it cost to check one blog post?

A gate call and an audit pull together are about 3 credits, roughly $0.0003. A hundred posts a month cost around three cents. Your CI minutes are billed by your CI provider, not by us.

Can I use the free actions in a pipeline?

Yes. domain, overview, stats and suggest need no key and no credit. For many gates that is enough, and you only pay when you pull lists of referring domains or anchors.

How fresh is the data?

Refreshed roughly once a month, so a link added last week may be missing. Design alerts around that and compare month to month rather than hour to hour.

Does it replace Ahrefs, Semrush or Moz?

No. Those suites cover keywords, rank tracking and a fresher crawl. This API covers link data at a low per-call price, and our DR is our own metric, not their numbers.

What happens when the credit runs out mid-job?

The API returns HTTP 402. Make your script stop and alert, because retrying cannot help. Top up with USDT (TRC-20) from the account page and re-run the failed batch.