# SaaS Review Tracker — full documentation for LLMs SaaS Review Tracker (https://reviews.saas.group) monitors public review profiles and marketplace rankings across eight platforms and makes the collected data available three ways: in the web app, through a REST API, and through an MCP (Model Context Protocol) server that AI assistants such as Claude, Cursor, ChatGPT and n8n can call directly. Built and maintained by saas.group. ## Supported platforms | Channel type | Platform | Identifier used as `slug` | |---|---|---| | g2 | G2 | product slug from g2.com/products/ | | shopify | Shopify App Store | app handle from apps.shopify.com/ | | wordpress | WordPress.org plugin directory | plugin slug from wordpress.org/plugins/ | | atlassian | Atlassian Marketplace | app slug (numeric app id also supported) | | omr | OMR Reviews | product slug from omr.com/en/reviews/product/ | | trustpilot | Trustpilot | business domain from trustpilot.com/review/ | | capterra | Capterra | product slug (numeric product id also used in URLs) | For every tracked profile the platform stores: name, average rating, total review count, star distribution where published, individual reviews (rating, title, body, author name, review date, vendor or developer reply where present), and dated snapshots of rating and review count so history can be charted. Platform-specific extras: active installations (WordPress), TrustScore (Trustpilot), numeric app or product ids (Atlassian, Capterra). Rankings are tracked per platform as either keyword positions (Shopify, WordPress, Atlassian, Trustpilot) or category leaderboard positions (G2, OMR, Capterra). Each check stores your position plus the competing entities listed around you. ## Refresh cadence Tracked profiles and keywords refresh on an automated daily schedule, and can also be refreshed on demand from the relevant page in the app. Each refresh writes a snapshot. ## Authentication and access - REST API: send a personal API key in the `x-api-key` header. - MCP: the same API key, passed as a header by the MCP client, or an OAuth flow for clients that support it. - Every account gets REST access and MCP access, each with its own key. - Data scope: an account reads the public profiles (saas.group and example profiles) plus the profiles and keywords it tracks. An administrator can widen an account's scope to all tracked entities. The exact API base URL and a personal key are shown on the API Docs page inside the app (https://reviews.saas.group/api) for accounts with access. ## REST API ### List tracked entities for a channel `GET {BASE_URL}/get-entity-data?type={type}` Query parameters: - `type` (required): one of g2, shopify, wordpress, atlassian, omr, trustpilot, capterra. - `limit` (optional): max results, default 100, max 1000. Example: ```bash curl "{BASE_URL}/get-entity-data?type=g2" -H "x-api-key: YOUR_API_KEY" ``` ### Get one entity with reviews and history `GET {BASE_URL}/get-entity-data?type={type}&slug={slug}` Query parameters: - `type` (required), `slug` (required). - `include` (optional): comma-separated `reviews`, `snapshots` (default: both). - `mode` (optional): `summary` (default; slim entity, no review bodies, weekly snapshots) or `full` (complete data, daily snapshots). - `reviews_limit` (default 25, max 100), `reviews_cursor`, `reviews_offset` (legacy). - `snapshots_limit`, `snapshots_cursor`, `snapshots_offset` (legacy). - `snapshots_granularity`: `daily` | `weekly` | `monthly`. Responses include `reviews_page` and `snapshots_page` blocks with `{ limit, offset, cursor, next_cursor, returned, total, has_more }`. To read everything, pass the previous response's `next_cursor` back as `reviews_cursor` / `snapshots_cursor` until `has_more` is false. Cursors are opaque; forward them verbatim. Example: ```bash curl "{BASE_URL}/get-entity-data?type=shopify&slug=advanced-shipping-manager&include=reviews,snapshots&mode=summary&reviews_limit=25" \ -H "x-api-key: YOUR_API_KEY" ``` Example response shape: ```json { "success": true, "type": "shopify", "entity": { "name": "Advanced Shipping Manager", "handle": "advanced-shipping-manager", "average_rating": 4.8, "total_reviews": 320 }, "reviews": [ { "rating": 5, "title": "…", "body": "…", "author_name": "…", "review_date": "2026-08-21", "vendor_reply": "…" } ], "snapshots": [ { "average_rating": 4.8, "total_reviews": 318, "scraped_at": "2026-08-17T06:00:00Z" } ], "reviews_page": { "limit": 25, "returned": 25, "total": 320, "has_more": true, "next_cursor": "…" } } ``` ### Error responses | Status | Meaning | |---|---| | 401 | Invalid or missing API key | | 400 | Invalid or missing `type` parameter | | 404 | Entity not found for the given slug | | 500 | Internal server error | ## MCP server Endpoint: `{BASE_URL}/mcp` — same API key as the REST API. Client configuration (Claude Desktop, Cursor, and other stdio clients): ```json { "mcpServers": { "saas-tracker": { "command": "npx", "args": ["-y", "mcp-remote", "{BASE_URL}/mcp", "--header", "x-api-key:YOUR_API_KEY"] } } } ``` Tools: - `list_channels` — supported channel types. - `list_entities` — args: `type`, optional `limit`. - `get_entity` — args: `type`, `slug`, optional `include`, `mode`, `reviews_limit`, `reviews_cursor`, `snapshots_limit`, `snapshots_cursor`, `snapshots_granularity`. - `list_rankings` — args: `type`, `slug`, optional `keyword`, `limit` (default 100, max 500), `offset`. Returns keyword or category ranking history newest-first. Supported for shopify, wordpress, atlassian, trustpilot, capterra and omr; G2 category leaderboards are not exposed through this tool. - `add_entity` — args: `type`, `identifier` (public profile URL or bare slug/handle/domain), optional `name`, `app_id` (required for Atlassian unless the full marketplace URL is passed), `product_id` (required for Capterra unless the full /p/// URL is passed). Starts tracking a new profile and queues the first scrape. Returns `scrape_status: "pending"`, or `already_exists: true` when the profile is already tracked. - `get_scrape_status` — args: `type`, `slug` or `id`. Returns `scrape_status` (`pending` | `running` | `completed` | `failed`), `last_scraped_at`, `scrape_error`, `total_reviews`, `average_rating` and `ready`. - `refresh_entity` — args: `type`, `slug` or `id`. Queues a fresh scrape (max one per 10 minutes per profile). Recommended write flow: `add_entity` → poll `get_scrape_status` every ~15 seconds until `ready: true` → then read with `get_entity` / `list_rankings`. Regular accounts may track up to 3 profiles in total; admins and accounts with extended data scope are unlimited. Typical prompts once connected: "list the newest G2 reviews for Rewardful", "how did our Shopify keyword rank change this month", "compare our Capterra and G2 ratings". ### Write actions (REST) `POST {BASE_URL}/get-entity-data` with the `x-api-key` header and a JSON body: ```json {"action": "add", "type": "g2", "identifier": "https://www.g2.com/products/rewardful"} ``` ```json {"action": "status", "type": "g2", "slug": "rewardful"} ``` ```json {"action": "refresh", "type": "g2", "slug": "rewardful"} ``` `add` accepts a public profile URL or bare slug/handle/domain (aliases: `url`, `slug`), plus optional `name`, `app_id` (Atlassian) and `product_id` (Capterra). `status` and `refresh` accept `slug` or `id`. `status` returns `ready: true` once the first scrape has finished. `refresh` is limited to one run per 10 minutes per profile. ### Access, limits and errors Every account gets REST API access and MCP access. An account sees the public profiles (saas.group and example profiles) plus the profiles and keywords it tracks; profiles a user adds stay private to them. An administrator can widen an account's data scope to all tracked entities. - 401 — invalid or missing API key. - 403 — API/MCP access not enabled, no access to that profile, or the 3-profile tracking limit reached. - 400 — invalid or missing `type`, unparseable `identifier`, or invalid `action`. - 404 — entity not found for the given slug. - 429 — refresh requested less than 10 minutes after the last scrape. - 500 — internal server error. ## Platform notes - G2: no free open reviews API exists for arbitrary products; vendor responses and star distribution are captured. Category leaderboards are tracked with full competitor sets. - Shopify App Store: no public API for reading a listing's reviews or search position; organic keyword position and competing apps are recorded per check. - WordPress.org: the public plugin API returns current metadata only; this platform adds review history, active-installation history and directory search rank history. - Atlassian Marketplace: the Marketplace API covers app metadata; review and rank history are added here. - OMR Reviews: no public API; review text is stored in the original language. - Trustpilot: official APIs require a paid plan and cover your own profile only; TrustScore history and company replies are captured here. - Capterra: no open public API; category positions and review detail are captured. ## Guide pages - https://reviews.saas.group/guides - https://reviews.saas.group/guides/g2-reviews-api - https://reviews.saas.group/guides/shopify-app-store-reviews-api - https://reviews.saas.group/guides/wordpress-plugin-reviews-api - https://reviews.saas.group/guides/atlassian-marketplace-reviews-api - https://reviews.saas.group/guides/omr-reviews-api - https://reviews.saas.group/guides/trustpilot-reviews-api - https://reviews.saas.group/guides/capterra-reviews-api