API Reference - Hado SEO

The API is currently in beta. Endpoints and behavior are subject to change.

The Hado SEO API lets you programmatically invalidate cached pages so search engines always see your latest content, export your crawl analytics as JSON, and manage your routing rules (redirects and proxies). When you purge a page, Hado SEO immediately re-renders it and stores fresh HTML in the cache — no waiting for the next bot visit.

Base URL

All API requests are made to:

https://api.hadoseo.com/functions/v1

Available Endpoints

Purge Cache

Re-render a specific page and refresh its cached HTML

Export Analytics

Export granular per-bot analytics for all your domains as JSON

Export Crawl Analytics

Export verified/declared crawl totals per bot, with intent taxonomy

Export Crawl Logs

Export the raw per-request bot crawl log as JSON, CSV, or parquet files

Export Page Analytics

Export page-level crawl counts — which pages bots hit, with tier splits

Export Page Snapshots

Export which rendered HTML version each bot was served for a page, day by day

Get Snapshot

Fetch the exact HTML a bot was served, by snapshot ID

Export AI Referrals

Export human visits arriving from AI answer surfaces (ChatGPT, Perplexity, …)

Bot Definitions

The published bot taxonomy — every intent bucket and the bots in it, versioned

Routing Rules

Routing rules are a REST resource nested under each domain, at /domains/{domainId}/routing-rules. Use GET to list or fetch, POST to create, PATCH to update, and DELETE to remove.

List Routing Rules

List every redirect and proxy rule on a domain

Get Routing Rule

Fetch a single rule by ID

Create Routing Rule

Add a 301/302 redirect or a proxy rule

Update Routing Rule

Change, pause, or re-prioritize a rule

Delete Routing Rule

Permanently remove a rule

Request Style

The API uses two styles:

Resources you manage, like routing rules, use standard REST: GET, POST, PATCH, and DELETE on /<resources> and /<resources>/{id}. Resources that belong to a domain live under it, like /domains/{domainId}/routing-rules/{ruleId}.
Actions and exports, like Purge Cache and the analytics exports, are POST requests with a JSON body.

Either way, requests and responses use JSON with camelCase field names. Errors return an error code and usually a human-readable message.

Quick Start

Create an API Key

Go to Settings → API Keys in your Hado SEO dashboard and create a new key. Copy it immediately — it’s only shown once.

Purge a page

curl -X POST https://api.hadoseo.com/functions/v1/purge-cache \
  -H "Authorization: Bearer hado_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "yourapp.com",
    "path": "/about"
  }'

Verify

The response confirms the re-render job is queued. Fresh HTML will be available in cache within seconds.

Common Use Cases

Use Case	When to Purge
CMS content update	After publishing or editing a blog post
Product page change	After updating pricing, images, or descriptions
Landing page deploy	After pushing changes to your app

Rate Limits

All API calls are subject to per-minute and monthly rate limits based on your plan. See Authentication for details.

​Base URL

​Available Endpoints

Purge Cache

Export Analytics

Export Crawl Analytics

Export Crawl Logs

Export Page Analytics

Export Page Snapshots

Get Snapshot

Export AI Referrals

Bot Definitions

​Routing Rules

List Routing Rules

Get Routing Rule

Create Routing Rule

Update Routing Rule

Delete Routing Rule

​Request Style

​Quick Start

​Common Use Cases

​Rate Limits

Base URL

Available Endpoints

Routing Rules

Request Style

Quick Start

Common Use Cases

Rate Limits