SEB API

Read Your GrowSEB Data With an API Key

Projects, tracked rankings, site-audit issues, saved keyword research, Search Console and Google Analytics, from your own scripts, dashboards and tools, and an SEO check on every pull request's preview. The API never spends from your SEB Wallet.

Create an API Key
Getting Started

Three Steps

API keys come with every plan. A key reads one workspace, with your access to it.

  1. 1. Create a key in the app under Settings → API Keys. Copy it when it's shown: GrowSEB keeps only a fingerprint of it, so it can't be shown again.
  2. 2. Send it as a bearer token on every request, to https://app.growseb.com/api/v1.
  3. 3. Revoke it on the same page when it's no longer needed: it stops working at once.
curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://app.growseb.com/api/v1/projects

Using Claude, Cursor or another AI assistant? The same key connects it through the GrowSEB MCP server.

Endpoints

What You Can Read

Every endpoint here is a GET. Replace {id} with a project id from /projects.

GET/projects

The workspace's projects you can see: name, domain, country and language.

GET/projects/{id}

One project, with how many keywords it tracks and its latest site health score.

GET/projects/{id}/rankings

Tracked keywords (SEB Radar): the latest Google position, the change since the check before, and the ranking URL.

  • days: 0–90, adds each check's position in that window
  • page, per_page: up to 500 a page (100 by default)

GET/projects/{id}/audit

The latest completed site audit (SEB Sentinel): the health score, and the issues grouped by rule, the ones to fix first first, each with up to five affected URLs.

  • limit: up to 200 issue types (50 by default)

GET/projects/{id}/keyword-research

Keyword research saved in the project (SEB Discover and Keyword Magic), newest first, each with its top keywords: volume, difficulty, CPC and intent.

  • limit: up to 50 searches (20 by default)
  • keywords: up to 200 a search (25 by default)

GET/projects/{id}/search-console

The project's Search Console: clicks, impressions, CTR and average position, with the top 25 queries and pages.

  • days: 7–90 (28 by default)

GET/projects/{id}/analytics

The project's Google Analytics 4 property: sessions, users, page views, engagement and conversions, with the top traffic sources.

  • days: 7–90 (28 by default)
CI Audits

Check Every Pull Request's Preview

SEB Sentinel's checks on up to 50 pages of a preview, from your CI. The build fails when the health score drops below your bar.

POST/projects/{id}/ci-audits

Starts a CI audit of a preview: SEB Sentinel's checks on up to 50 pages, in the background. Answers 202 with the audit's id. Needs a key made with "Allow actions".

  • url: the preview's address (required)
  • max_pages: 1–50 (25 by default)
  • render_js: true to render pages in Chrome first

GET/projects/{id}/ci-audits/{audit}

One CI audit: its status (pending, crawling, completed or failed), and once completed its health score, counts, and the issues grouped by rule, the ones to fix first first.

  • limit: up to 100 issue types (50 by default)

GET/projects/{id}/ci-audits

The project's CI audits, newest first, without their issues.

  • limit: up to 100 (20 by default)
curl -X POST -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://my-site-git-new-pricing.vercel.app", "max_pages": 25}' \
  https://app.growseb.com/api/v1/projects/123/ci-audits

Your CI starts the audit, reads it until its status is completed or failed, and fails the build when health_score is below your bar.

  • Links, canonicals and sitemap entries that name your live domain are read as the same page on the preview. The X-Robots-Tag: noindex header that preview hosts send isn't judged; a robots meta tag is.
  • CI audits stay out of the project's audit history, change alerts, dashboard and reports. The API keeps them for 90 days.
  • One runs at a time per project. The preview must be open to anyone: one behind a login, or Vercel's Deployment Protection, fails with the reason.
  • Each counts toward the plan's CI audits a month: Growth 150, Pro 900, Agency 3,000. A failed one doesn't count.
Responses

One Shape for Every Answer

Success carries data (and meta for lists); a failure carries an error code you can act on.

{
  "success": true,
  "data": [
    { "id": 2, "name": "Laabam.one", "domain": "www.laabam.one", "country": "in", ... }
  ],
  "meta": { "count": 1 }
}
{
  "success": false,
  "error": { "code": "rate_limited", "message": "Too many requests for this key. ..." }
}
StatusCodeMeaning
401unauthenticatedNo key, or a key that has been revoked.
402plan_limitThis month's CI audits are used: they reset on the 1st.
403plan_requiredThe workspace's plan doesn't include the API.
403workspace_forbiddenYou're no longer a member of the key's workspace.
403read_only_keyStarting a CI audit needs a key made with "Allow actions".
403not_allowedThe key's owner can no longer make changes in the workspace (a viewer).
404not_foundNo such project for this key.
409busyA CI audit of the project is running: the Retry-After header says when to try again.
422validation_failedA parameter is missing or wrong: the message names it.
422unreachableThe preview's address isn't on the public internet, or has no DNS record.
404not_connectedSearch Console or Google Analytics isn't connected for the project.
429rate_limitedOver the key's requests a minute: the Retry-After header says when to try again.
502google_unavailableGoogle couldn't be read just now: try again later.
Rate Limits

Requests a Minute, per Key

Over the limit, the API answers 429 with a Retry-After header. Search Console and Google Analytics answers are kept for an hour.

PlanRequests a minute
Free10
Basic20
Starter30
Growth60
Pro120
Agency300
Enterprise600

What the API Doesn't Do Yet

Besides CI audits, it reads only. Auditing the live site, looking up new keywords or writing content still happens in the app, or through your AI assistant. Tell us what you'd automate next.

Tell Us What You Need