Two new reference-data endpoints let you look up the location and
language values that POST /v1/domains/{domain_uuid}/keywords accepts,
keyword create now takes an ISO country code for country-wide tracking, and
its 422 responses name the failing field and how to fix it.
The search_engines[].location examples throughout these docs showed a
location name — "United States" — as the value to send when creating
keywords. That value has never been accepted by the API; it always returned
422. The examples have been corrected.
Rate-limited requests now respond with 429 Too Many Requests instead of
503 Service Unavailable, and carry a Retry-After header telling you exactly
how long to wait.
If your client branches on 503 to detect throttling, update it to 429.
The Ranktracker REST API (v1) is now publicly documented. It gives you API-key–authenticated access to your rank-tracking data:
Head to the Quickstart to make your first request.