XenonFlare

Developer API

Backlink API — queue discovery and sync jobs per property

Queue discovery and sync jobs, poll jobs, and read new/lost link diffs from the workspace — same as the app.

Async jobs

Two job types — discovery finds links, sync verifies them

backlink-discovery runs Common Crawl and mention search; Backlink sync probes candidates and writes snapshot diffs to your property index.

Quick start (curl)

Replace $XF_API_KEY and property IDs with values from your workspace. Full reference: Developer API docs.

curl -s -H "Authorization: Bearer $XF_API_KEY" \
  https://api.xenonflare.com/api/v1/properties/$XF_PROPERTY_ID/backlinks/workspace

Créer son propre crawler vs l’API XenonFlare

Développez en interne quand…

  • Common Crawl CDXcandidate queues, probe infrastructure, and dedupe
  • Referring-domain expandbounded spiders and monthly quota metering
  • Snapshot diffsdurable link index, retention, and new/lost tracking
  • Job orchestrationdiscovery vs sync lanes, schedulers, and idempotent enqueue

Utilisez XenonFlare quand…

  • POST backlink-discoveryand gsc-links-sync jobs per property
  • GET workspace + statsqueue depth, sources, and monthly quota remaining
  • Scheduled discoveryon Growth+ with same verify pipeline
  • Agency portfoliosunlimited syncs and 100 discovery queries/mo on Agency

Typical API integration

  1. Create a Starter+ workspace and API key with jobs:write and properties:read
  2. Resolve property IDs via GET /properties
  3. POST …/jobs/backlink-discovery then POST …/jobs/gsc-links-sync
  4. Poll GET /jobs/:id until completed; read workspace for link diffs

Ce que vous obtenez

Snapshot, queue stats, and monthly usage

Candidate counts by source and quota remaining

Common Crawl + web mention candidate enqueue

Verify candidates and persist new/lost/broken diffs

Scoped Bearer keys

properties:read, jobs:write; same rate limits as audits

Agency portfolios

Unlimited syncs, 100 discovery queries/mo per org

FAQ

Which endpoints enqueue backlink jobs?

POST /properties/:id/backlinks/jobs/backlink-discovery and POST …/jobs/gsc-links-sync. Both return 202 with a job id to poll via GET /jobs/:id.

Is Google Search Console Links available via API?

No. Google does not expose the Links report publicly. XenonFlare discovery uses Common Crawl and mention search; GSC top pages only seed on-site crawl paths.

How is this different from Ahrefs or Moz APIs?

XenonFlare builds a per-property index you manage — not a global backlink database for arbitrary competitor domains. See /backlink-monitoring.

Which plan includes the Backlink API?

Developer API keys require Starter or above. Discovery and sync quotas follow plan limits — Growth adds scheduled jobs; Agency raises caps.

Backlink API on paid workspace plans

Create API keys after upgrading to Starter. Free tier includes the dashboard — not REST job enqueue for backlinks.