# Atlassian Marketplace Monitor — Releases & Pricing (`xqfech/atlassian-marketplace-monitor`) Actor

Watches Atlassian Marketplace (Jira, Confluence, Bitbucket apps) between runs. Detects new apps, version releases, payment model changes, rating and install movements as structured field-level change events.

- **URL**: https://apify.com/xqfech/atlassian-marketplace-monitor.md
- **Developed by:** [Emmanuel Obiefule](https://apify.com/xqfech) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 change events

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Atlassian Marketplace Monitor — Track App Releases, Pricing Models & Ratings

The Atlassian Marketplace is a 5,000+ app ecosystem where vendors ship paid releases every week. This Actor watches it **between runs** and reports what changed: new apps in your niche, version releases, payment-model switches (free → paid is a signal you want the same day), rating and install movement — as structured change events with field-level before/after diffs.

Built on the official Marketplace REST API. No scraping fragility, no login, runs in seconds.

### What it does

- **Watch a niche** — search terms (`time tracking`, `test management`) or whole products (`jira`, `confluence`). Every run diffs the app set against the previous run: `new_addon`, `removed_addon`, `addon_changed`.
- **Watch specific apps** — track competitors by addon key: latest version, payment model, deployment targets (Cloud / Data Center), rating, review count, install base, vendor and category changes.
- **Noise-controlled** — install and review counters are banded to meaningful magnitudes; ratings rounded — you only see events worth acting on.

### Who uses this

- **Marketplace vendors** — the Atlassian app economy is competitive and paid; know the day a rival ships, changes pricing model, or starts gaining installs.
- **Atlassian admins & platform teams** — version-change events for the apps your instance depends on.
- **Investors & analysts** — category dynamics for one of the largest paid B2B app ecosystems.

### Output example

```json
{
  "type": "addon_changed",
  "source": "watch",
  "key": "com.onresolve.jira.groovy.groovyrunner",
  "name": "ScriptRunner for Jira",
  "url": "https://marketplace.atlassian.com/apps/6820",
  "changes": [
    { "field": "version", "before": "39.0.0", "after": "39.1.0" },
    { "field": "installs", "before": 34000, "after": 35000 }
  ],
  "detectedAt": "2026-08-04T10:00:00.000Z"
}
```

### Input

| Field | Description |
| --- | --- |
| `applications` | Products watched as full app sets (jira, confluence, …) |
| `searchTerms` | Search queries watched as result sets |
| `addonKeys` | Specific apps tracked with field diffs |
| `maxResultsPerList` | Result set size per list (10–1000) |
| `monitorId` | State namespace shared between runs |

### Reliability

Official `marketplace.atlassian.com/rest/2` JSON API only — no markup to break. Strict schema validation on every item; the run fails loudly rather than storing garbage. First run stores a baseline; change events start from run two.

### Scheduling

Run daily via an Apify Schedule and pipe events to Slack, email, webhooks, or Google Sheets through Apify integrations. Quiet days produce no change events and cost almost nothing.

# Actor input Schema

## `applications` (type: `array`):

Atlassian products: jira, confluence, bitbucket, jira-service-management. Watches the full app list per product (up to max results).

## `searchTerms` (type: `array`):

Each term is watched as a result set: new apps entering, apps leaving, field changes.

## `addonKeys` (type: `array`):

Exact addon keys (e.g. com.onresolve.jira.groovy.groovyrunner). Tracks version, payment model, deployment targets, rating and installs with field-level diffs.

## `maxResultsPerList` (type: `integer`):

Maximum number of items collected per watched list.

## `monitorId` (type: `string`):

State namespace. Runs with the same Monitor ID share the previous-run snapshot.

## `emitBaseline` (type: `boolean`):

On the very first run the full initial snapshot is pushed as baseline items so you still get data.

## Actor input object example

```json
{
  "searchTerms": [
    "time tracking"
  ],
  "addonKeys": [
    "com.onresolve.jira.groovy.groovyrunner"
  ],
  "maxResultsPerList": 100,
  "monitorId": "default",
  "emitBaseline": true
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchTerms": [
        "time tracking"
    ],
    "addonKeys": [
        "com.onresolve.jira.groovy.groovyrunner"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("xqfech/atlassian-marketplace-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchTerms": ["time tracking"],
    "addonKeys": ["com.onresolve.jira.groovy.groovyrunner"],
}

# Run the Actor and wait for it to finish
run = client.actor("xqfech/atlassian-marketplace-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchTerms": [
    "time tracking"
  ],
  "addonKeys": [
    "com.onresolve.jira.groovy.groovyrunner"
  ]
}' |
apify call xqfech/atlassian-marketplace-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=xqfech/atlassian-marketplace-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ODXFVnlHbIbp7b5kK/builds/eQTTP8wj5LXkogMC7/openapi.json