SearchChampAPI overview
Use SearchChamp's read-only REST API from reporting tools, internal scripts, and custom integrations.
The SearchChamp REST API gives your own software read-only access to rankings, tracked keywords, AI Visibility, and site-audit summaries. It is designed for reporting and data integrations. It is separate from the MCP connector, which exposes tools to AI clients.
Four REST endpoints is the complete current public surface
The endpoint reference is not a partial list. SearchChamp currently exposes exactly four public REST routes. Content Writer and Research Studio application endpoints are not public API contracts. Some Content Writer, publishing, research-assistance, and broader SEO workflows are available through MCP instead. See feature coverage before choosing an integration.
Availability
The public REST API requires a Pro plan or higher and an API key with the Read permission. Trial, Starter, and other below-floor plans cannot call these routes.
Base URLs
| Environment | Base URL |
|---|---|
| Production | https://api.searchchamp.com |
| SearchChamp development/testing | https://api-dev.searchchamp.dev |
Use the environment that contains the organization and sites you want to read. API keys are environment-specific.
Quick start
- Create an API key under Settings → API Keys and save the value beginning with
atl_. - Export it from your shell instead of putting it in source code.
- Call a route with your site's exact domain or slug.
export SEARCHCHAMP_API_KEY='atl_your_key_here'
curl --fail-with-body \
--get 'https://api.searchchamp.com/v1/api/rankings' \
--header "Authorization: Bearer $SEARCHCHAMP_API_KEY" \
--data-urlencode 'site=example.com' \
--data-urlencode 'days=7' \
--data-urlencode 'limit=10'A successful response uses the common envelope:
{
"data": {
"site": "example.com",
"days": 7,
"movers": []
},
"meta": {},
"errors": []
}Read next
- Feature coverage: REST, MCP, or app — see which integration surface supports each SearchChamp feature.
- Authentication and API keys — permissions, expiry, revocation, and secret handling.
- Endpoint reference — every supported route, parameter, and response.
- Errors, limits, and usage — error envelopes, rate limits, metering, and retry guidance.
Current boundary
The v1 public surface contains four GET routes. It has no public write endpoints, Content Writer generation endpoint, Research Studio session endpoint, webhooks, pagination cursors, or idempotency keys. Do not call the internal endpoints used by the SearchChamp web app; they are not part of the public contract and can change without notice.