RankSharkDocs

Changelog

What changed in the RankShark Track and Enhance REST APIs and MCP servers, month by month, and how we announce changes that could break your code.

We add fields and endpoints without notice. Write code that ignores fields it does not know. Anything that could break existing code is announced here first.

November 2026

  • Public developer docs at docs.rankshark.io, with a full reference for the Track and Enhance APIs.
  • Enhance MCP tools are named enhance_…, for example enhance_list_campaigns.
  • Enhance: locations. List the places a campaign can target visits to, over REST and MCP.
  • Enhance: status. GET /api/v1/status and GET /api/v1/meta say whether your subscription is active.
  • Error links. Enhance error bodies carry a type link to their code on the Errors page.
  • Track: several engines per campaign. engines takes a list (for example ["maps", "search", "ai"]), each keyword is scanned on each engine, and aiGrid sets the grid for AI answers.
  • Track: scans show their wait. wait.ahead, wait.startsInMin and wait.minutesLeft tell you when a queued scan starts and finishes.

October 2026

  • Track API and MCP server at /v1/track and /mcp/track, with their own keys (rstk_…) and scopes.
  • Enhance keys now start with rsen_. Older Enhance keys keep working.
  • OAuth sign-in for Claude.ai, ChatGPT and other MCP clients, for both products.

On this page