# Steam Player Count Scheduled Monitor

**Use case:** 

Reuse a named snapshot store across scheduled runs to calculate changes in live Steam player counts.

## Input

```json
{
  "appIds": [
    "730",
    "570"
  ],
  "includeAppDetails": true,
  "country": "us",
  "language": "english",
  "snapshotStoreName": "steam-player-watchlist",
  "maxConcurrency": 4,
  "maxRequestRetries": 3
}
```

## Output

```json
{
  "appId": {
    "label": "App ID",
    "format": "number"
  },
  "name": {
    "label": "Game",
    "format": "text"
  },
  "currentPlayerCount": {
    "label": "Current players",
    "format": "number"
  },
  "previousPlayerCount": {
    "label": "Previous players",
    "format": "number"
  },
  "absoluteChange": {
    "label": "Player change",
    "format": "number"
  },
  "percentChange": {
    "label": "Change (%)",
    "format": "number"
  },
  "developers": {
    "label": "Developers",
    "format": "array"
  },
  "publishers": {
    "label": "Publishers",
    "format": "array"
  },
  "genres": {
    "label": "Genres",
    "format": "array"
  },
  "releaseDate": {
    "label": "Release date",
    "format": "text"
  },
  "recommendationCount": {
    "label": "Recommendations",
    "format": "number"
  },
  "observedAt": {
    "label": "Observed at",
    "format": "date"
  },
  "storeUrl": {
    "label": "Steam Store",
    "format": "link"
  },
  "playerCountSourceUrl": {
    "label": "Count source",
    "format": "link"
  },
  "error": {
    "label": "Error",
    "format": "text"
  }
}
```

## About this Actor

This example demonstrates how to use [Steam Live Player Count Monitor](https://apify.com/automation-lab/steam-live-player-count-monitor) with a specific input configuration. Visit the [Actor detail page](https://apify.com/automation-lab/steam-live-player-count-monitor) to learn more, explore other use cases, and run it yourself.


## 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.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/automation-lab/steam-live-player-count-monitor.md

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).