Getting started with the API

The SearchOps API lets you pull your data into your own tools, dashboards, or scripts. Version 1 is read-only, so it is a safe way to read your locations, keywords, rankings, AI Engine Visibility, reviews, citations, scans, and reports programmatically.

What you'll need

A plan that includes API access. The API is available on Pro and above.

Create an API key

Go to Developers > API & MCP Credentials in the dashboard. (The same card also appears under Settings > API & MCP.)
Enter a name for the key, such as "Reporting script" or "Zapier", and select Create key.
Copy the key straight away. It starts with lp_live_ and is shown once only, for security.

You can see your keys, when each was last used, and revoke any of them from the same card. Only account owners and admins can create keys.

Warning: Treat a key like a password. Never commit it to a public repository or put it in client-side code. If one is exposed, revoke it and create a new one.

Make your first request

Send your key as a bearer token in the Authorization header. For example, to list your locations:

curl https://searchops.co.uk/api/v1/locations \
  -H "Authorization: Bearer lp_live_your_key_here"

A successful response looks like:

{ "data": [ ... ], "pagination": { "limit": 50, "offset": 0 } }

If you get a 401, the key is missing, wrong, or revoked. A 403 means the key is fine but the plan on the account no longer includes API access. A 429 means you have gone over the rate limit of 120 requests a minute; that limit is counted per key, not per IP address, so calls from a shared host such as Zapier or a CI runner do not eat into each other's budget.

Every request you make, including the ones that fail, is listed under Developers > API Event Logs with its status, latency, and which key was used. That is the fastest way to see what an integration is actually sending.

What you can read (v1)

All endpoints are GET only:

/api/v1/locations and /api/v1/locations/{id}
/api/v1/locations/{id}/summary for every headline in one call
/api/v1/locations/{id}/keywords
/api/v1/locations/{id}/rankings
/api/v1/locations/{id}/chatgpt-visibility
/api/v1/locations/{id}/reviews
/api/v1/locations/{id}/citations
/api/v1/locations/{id}/competitors
/api/v1/scans and /api/v1/scans/{id}
/api/v1/reports and /api/v1/reports/{id}

List endpoints accept limit (up to 100) and offset for paging, and /scans accepts a locationId filter. Every key is scoped to your account, so you only ever read your own data.

The full reference, with parameters and example responses for each endpoint, is under Developers > API Documentation. If you would rather generate a client than write the calls by hand, the API is described by an OpenAPI document at /api/v1/openapi.json, which needs no key to read.

Note: Version 1 is read-only. It does not create scans or change data. Write access is planned for a future version.

Next steps

Want an agent to read your data through a standard protocol? See Connect the MCP server.