TabAPI

Every domain signal.
One API.

Traffic, WHOIS, RDAP, DNS, backlinks, and reverse-AdSense for any domain — plus Google SERPs, page-to-Markdown, and screenshots for any URL. Nine endpoints, one bearer token, bare JSON.

Get API keyTry playground
9
Endpoints
1
Bearer token
OpenAPI
Client generation

The catalog

Pick the signal you need.

9 endpoints behind one bearer token. Every one is documented, metered in credits, and runnable in the playground before you create an account.

Start with one request.
Meter every call.

One bearer header reaches all nine endpoints. Responses are the bare resource — snake_case JSON and ISO 8601 dates. Credit usage is recorded in your dashboard.

  • One bearer token, no signing
  • Usage history in the dashboard
  • Errors are never billed
Read full API docs
bash
# 1 — your key, once
export TABAPI_KEY="sk_live_…"

# 2 — any of the nine endpoints
curl "https://tabapi.com/api/v1/domains/vercel.com/dns?type=all" \
  -H "Authorization: Bearer $TABAPI_KEY"

# 3 — review usage in the dashboard
# https://tabapi.com/settings/credits
How credits worktransparent
  1. 1

    Check the cost

    Every endpoint shows its credit cost before you send a request.

  2. 2

    Send the request

    Use one API key across all nine endpoints and receive the documented JSON response.

  3. 3

    Review usage

    Successful requests deduct the listed credits and appear in your dashboard history.

  4. 4

    Keep credits on errors

    Failed requests and timeouts do not consume credits.

Credit-metered billing

You pay for data.
Never for failures.

Review your balance and per-request credit usage in the dashboard.

Platform

Built like infrastructure.

The behaviours you can write code against — documented consistently across every endpoint.

One key, every endpoint

A single Authorization: Bearer sk_ header reaches all nine endpoints. Keys are shown once, stored only as a hash, and rejected in query strings to reduce accidental exposure.

Usage in the dashboard

Every successful call is recorded in the dashboard, where you can review per-request consumption and your remaining balance.

You pay for data

Error responses are never charged, so credits leave your balance only when a lookup returns data.

Streaming for slow calls

Backlinks can stream over Server-Sent Events: the connection opens on a meta frame, results arrive in stages, and an empty done frame marks completion.

OpenAPI 3.1, generated clients

Use the OpenAPI 3.1 document at /api/v1/openapi.json with common generators to create a typed client for your stack.

Raced and edge-cached

DNS runs over DoH with Cloudflare and Google queried in parallel and successful answers preferred over DNS errors; repeat lookups may use cached data.

Credits

Pay once. Credits never expire.

$1 buys 1,000 credits. Spend them on any endpoint, whenever you like — they never expire.

  • Credits never expire
  • Only successful calls are charged
  • All 9 endpoints on one bearer token
  • No charge for failed requests

Select package

One-time payment · Never expires · ≈ 105,000 backlink profiles

Need more than $10,000? Contact us

FAQ

Questions engineers ask first

Anything else is in the full reference.

Ready to look it up?

Create a key, send one bearer-authenticated request, and read the answer back as bare JSON. Credits are one-time and never expire.

Get API key