saas.groupSaaS Review Tracker
    guidesatlassian marketplace re…
    Atlassian Marketplace logoAtlassian Marketplace

    Pull Atlassian Marketplace reviews and rankings via API or MCP

    Atlassian Marketplace exposes app metadata, but review history and search ranking movement are not available as a time series. SaaS Review Tracker monitors the apps you add and returns their reviews, ratings and keyword positions through a REST API and an MCP server.

    What data you can pull

    FieldTypeDescription
    namestringDisplay name of the tracked profile.
    average_ratingnumberCurrent average star rating.
    total_reviewsnumberTotal number of reviews counted on the profile.
    reviews[]arrayIndividual reviews: rating, title, body, author, review date, vendor reply.
    snapshots[]arrayHistorical daily/weekly/monthly snapshots of rating and review count.
    last_scraped_attimestampWhen the profile was last refreshed.
    app_idstringNumeric Atlassian Marketplace app id.
    star_distributionobjectShare of 5/4/3/2/1-star reviews on the app listing.

    Rankings: Atlassian Marketplace keyword rankings: your app’s position in marketplace search for each tracked keyword, with competitor apps captured per check.

    Pull Atlassian Marketplace reviews with the REST API

    Every request is authenticated with a personal API key sent in the x-api-key header. The slug parameter is the Marketplace app slug (with the numeric app id where needed).

    List tracked Atlassian Marketplace profiles

    curl "https://reviews.saas.group/api/v1/get-entity-data?type=atlassian" \
      -H "x-api-key: YOUR_API_KEY"

    Get one profile with reviews and history

    curl "https://reviews.saas.group/api/v1/get-entity-data?type=atlassian&slug=jira-misc-workflow-extensions&include=reviews,snapshots&reviews_limit=25" \
      -H "x-api-key: YOUR_API_KEY"

    Example response

    {
      "success": true,
      "type": "atlassian",
      "entity": {
        "name": "an Atlassian Marketplace app",
        "slug": "jira-misc-workflow-extensions",
        "average_rating": 4.8,
        "total_reviews": 320,
        "last_scraped_at": "2026-08-24T06:00:00Z"
      },
      "reviews": [
        {
          "rating": 5,
          "title": "<review title>",
          "body": "<review body text>",
          "author_name": "<reviewer name>",
          "review_date": "2026-08-21",
          "vendor_reply": "<vendor response, when present>"
    
        }
      ],
      "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": "eyJkIjoi..." }
    }

    Reviews and snapshots paginate independently. Follow reviews_page.next_cursor and snapshots_page.next_cursor until has_more is false.

    Read Atlassian Marketplace data from an AI assistant via MCP

    The Model Context Protocol server lets Claude Desktop, Cursor, ChatGPT, n8n and other MCP clients query the same data in natural language. Endpoint: https://reviews.saas.group/api/v1/mcp

    Client configuration

    {
      "mcpServers": {
        "saas-tracker": {
          "command": "npx",
          "args": [
            "-y", "mcp-remote",
            "https://reviews-mcp.saas.group/mcp",
            "--header", "x-api-key:YOUR_API_KEY"
          ]
        }
      }
    }

    Tool calls for Atlassian Marketplace

    // get_entity
    { "type": "atlassian", "slug": "jira-misc-workflow-extensions", "include": ["reviews", "snapshots"], "mode": "summary" }
    
    // list_entities
    { "type": "atlassian", "limit": 50 }
    
    // list_rankings — keyword/category ranking history
    { "type": "atlassian", "slug": "jira-misc-workflow-extensions", "limit": 50 }
    
    // add_entity — start tracking a new profile
    { "type": "atlassian", "identifier": "https://marketplace.atlassian.com/apps/1211438/jira-misc-workflow-extensions", "app_id": "1211438" }
    
    // get_scrape_status — poll until ready: true
    { "type": "atlassian", "slug": "jira-misc-workflow-extensions" }
    
    // refresh_entity — queue a fresh scrape (max 1 per 10 min)
    { "type": "atlassian", "slug": "jira-misc-workflow-extensions" }

    Available tools: list_channels, list_entities, get_entity, list_rankings, add_entity, get_scrape_status and refresh_entity. Once connected you can simply ask, for example, “summarise the newest Atlassian Marketplace reviews for an Atlassian Marketplace app”.

    list_rankings is available for Atlassian Marketplace and returns rank history newest-first, optionally filtered to a single keyword or category.

    Add a new Atlassian Marketplace profile via API or MCP

    You can start tracking a profile without opening the app. Pass the public profile URL (or the bare marketplace app slug (with the numeric app id where needed)) to add_entity. Accepted identifier formats: marketplace.atlassian.com/apps/<app_id>/<slug> — a bare slug also needs an app_id argument. The first scrape runs in the background, so poll get_scrape_status until it returns ready: true before reading reviews. Regular accounts can track up to three profiles in total.

    # 1. start tracking a profile
    curl -X POST "https://reviews.saas.group/api/v1/get-entity-data" \
      -H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
      -d '{"action":"add","type":"atlassian","identifier":"https://marketplace.atlassian.com/apps/1211438/jira-misc-workflow-extensions"}'
    
    # 2. poll until the first scrape finishes
    curl -X POST "https://reviews.saas.group/api/v1/get-entity-data" \
      -H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
      -d '{"action":"status","type":"atlassian","slug":"jira-misc-workflow-extensions"}'
    
    # 3. queue a later refresh (max one per 10 minutes)
    curl -X POST "https://reviews.saas.group/api/v1/get-entity-data" \
      -H "x-api-key: YOUR_API_KEY" -H "Content-Type: application/json" \
      -d '{"action":"refresh","type":"atlassian","slug":"jira-misc-workflow-extensions"}'

    If the profile is already tracked, the call succeeds with already_exists: true and returns the existing record. A refresh requested within 10 minutes of the last scrape returns 429; a profile another account tracks privately returns 403.

    Access and data scope

    Every account gets REST API and MCP access, and each account uses its own key.

    A key reads the public profiles (saas.group and example profiles) plus the profiles and keywords that account tracks. Profiles you add stay private to you. An administrator can widen an account’s data scope to all tracked entities.

    Create an account to start tracking Atlassian Marketplace profiles, then open the API & MCP reference to generate your key.

    See the live Atlassian Marketplace data

    Atlassian Marketplace API & MCP: frequently asked questions

    Other platforms