Use the public API

The RankMeFast public API gives Agency accounts read-only access to supported data the account already owns. Requests use a show-once bearer key, and the API does not start audits, rank checks, or other paid vendor work.

Before you start

• An Agency account and an API client that can send a bearer header.
• Existing RankMeFast data from sites, audits, or rank tracking to read.

Follow these steps

1. 1

   Create a dedicated key

   Open Account and API keys, create a descriptive key, and copy the full value immediately. Keep separate integrations on separate keys so one can be revoked cleanly.

2. 2

   Use the deployment API origin

   Build requests from the public server origin documented for your installation. Do not copy the rankme.fast host into a self-hosted integration.

3. 3

   Send bearer authentication

   Add the key to the Authorization header on every request. Do not place it in a URL, browser log, client-side bundle, or committed configuration file.

4. 4

   Read a stored-data endpoint

   Start with sites, then request a supported report, keyword, rank-history, SERP-feature, or backlink-row read. Cross-account and unknown resources return the same not-found behavior.

5. 5

   Follow formats and cursors

   Use the documented JSON or available CSV contract, preserve stable columns, and follow an opaque next cursor only when the response provides one. Do not invent or edit cursor values.

6. 6

   Handle limits and rotate

   Respect error status and rate-limit headers, retry only when appropriate, and create a replacement key before revoking an old one. Revocation takes effect immediately.

What you get

• Owner-scoped reads of supported stored RankMeFast data.
• Documented JSON and available CSV contracts without hidden vendor jobs.
• Independently revocable credentials for each integration.

Common questions

Related guides