Overview

The Aggregator Machine API (1)

B2B game aggregation platform. Server-to-server REST API for operators to browse the game catalog, launch real-money and demo sessions, and query transactions.

How to call this API: business endpoints share the base URL https://api.aggregator.gg/v1. The /health and /ready probes are the one exception: they are served at the API root (https://api.aggregator.gg), without the /v1 prefix. Authorize every business call with an Authorization: Bearer header, keeping the key in a protected environment variable. The shell builtin printf passes the header through stdin so the key is not included in curl’s arguments:

(
  if [ -z "${AGGREGATOR_API_KEY:-}" ]; then
    printf '%s\n' 'Set AGGREGATOR_API_KEY before calling the API.' >&2
    exit 1
  fi
  printf 'Authorization: Bearer %s\n' "$AGGREGATOR_API_KEY" |
    curl -H @- "https://api.aggregator.gg/v1/games?per_page=5"
)

Authentication: Bearer token via Authorization header. New operator API keys are prefixed agg_*; older keys keep working until revoked. If welcome credits are enabled for your account, real-money sessions still involve wallet operations. Use demo sessions for non-financial testing; see https://hub.aggregator.gg/environments/.

Versioning: path version (/v1/) in the URL. See https://hub.aggregator.gg/getting-started/.

Idempotency: POST endpoints touching financial state require an Idempotency-Key header. Reuse the same key and request body when retrying one logical operation. /sessions returns the stored response for the same key for 24 hours. /free-rounds returns the stored grant for the same key and request, and 409 if the key is reused with a different request.

• Aggregator API support: https://hub.aggregator.gg - support@aggregator.gg
• License: Proprietary
• OpenAPI version: 3.1.0

Authentication

bearerAuth

Security scheme type: http

Bearer format: agg_* (older sk_live_* and sk_test_* keys also work)