Developer API

DomainShark API (coming soon)

Programmatic access to the SharkDEX dataset. In active build. Production launch later in 2026.

We're building a clean, versioned REST API on top of the same SharkDEX dataset that powers domainshark.com.au. It is designed for agencies, brokers, researchers, registrar partners and indie tools who need machine access to Australian drop data without scraping our pages. There will be a small, free demo tier so you can sanity check the shape before committing to a paid plan.

What you'll be able to do

  • check live availability for a specific .au domain;
  • search the SharkDEX with filters (TLD, length, hyphens, numbers, score) and proper pagination;
  • pull the just-dropped feed since a timestamp you choose, for portfolio monitoring;
  • request the full report card data behind /domain/<name>, length, age, hyphens, numbers, Wayback presence, SharkDEX score;
  • read public dataset stats (records tracked, available now, last refresh) without authentication;
  • on higher tiers, subscribe to signed webhook deliveries when domains drop.

Indicative tiers

Final tier names, request limits and prices are still being calibrated. Today's working shape:

  • Demo (no key required), low per-IP rate limit, single-record responses, restricted fields, no pagination. For evaluation only.
  • Member (free account, key required), modest hourly limit, restricted shape. Good for hobby projects.
  • Starter (paid, AUD/month), list endpoints with full fields, sensible monthly cap, 25 results per page.
  • Pro (paid, AUD/month), higher monthly cap, 100 per page, signed webhook deliveries for domain.dropped events.
  • Firehose (bespoke), bulk export, daily diffs, contractual SLA. Talk to us.

Final pricing will be published here at launch. Anything you see in legal copy referencing the API is the framework we'll launch on, see Terms §16 and Acceptable Use §3.

Authentication and shape (planned)

  • Bearer tokens (Authorization: Bearer ds_live_…) issued from /profile/api-keys, hashed at rest.
  • JSON request and response. ISO-8601 UTC timestamps. Errors as { "error": { "code", "message", "request_id" } }.
  • Versioned URL path: /api/v1/<resource>. Breaking changes go to /v2 with at least a 90-day deprecation window on the previous version.
  • 429 responses include Retry-After. 5xx responses should be retried with backoff.
  • OpenAPI 3.1 schema served from /api/v1/openapi.json, with an embedded explorer on this page.

Endpoint shape (planned)

GET  /api/v1/stats
GET  /api/v1/domains/check?domain=example.com.au
GET  /api/v1/search?q=coffee&tld=com.au&page=1&per_page=25
GET  /api/v1/dropped?since=2026-05-15T00:00:00Z&limit=100
GET  /api/v1/domains/{domain}
POST /api/v1/webhooks   (Pro tier and above)

Early access

If you'd like a heads up when the API opens, or you have a specific integration need we should factor in, send us a note via the contact form with “API early access” in the subject line. Tell us roughly what you'd build and the volume you'd expect, that helps us prioritise endpoints and right-size the launch tiers.

We'll publish the launch list here, the OpenAPI schema, and live curl examples once the demo tier is open.

Related