REST API fallback

🔌 This is a fallback, not an alternative integration path. Autoplay MCP is how you connect an agent — it’s the only way to reach onboarding progress, proactivity criteria, guided tours, and confirmed completions. Use this endpoint only when your platform can’t speak MCP but can call an external HTTP endpoint (for example a chatbot builder that only supports “custom actions”). You never need both.

This endpoint returns a user’s recent in-app footsteps — pages viewed, buttons clicked, forms submitted — as the same envelope get_live_user_activity returns over MCP.

🌐 The endpoint

GET https://mcp.autoplay.ai/users/{product_id}/{user_id}/live-activity

Part	Meaning
`{product_id}`	Your Autoplay product id — the same `YOUR_PRODUCT_ID` you registered in the Quickstart.
`{user_id}`	The stable user identifier your activity source stamps events with (the id you pass to `posthog.identify(...)`; the Amplitude `user_id`; …). This match is the linchpin — see Identity.
`?limit=`	Optional. Max recent actions to return. Omitted or `<= 0` falls back to the configured cap (50).

Auth — Authorization: Bearer YOUR_MCP_KEY (the mcp_key from your Quickstart product registration).

401 — token missing or invalid.
403 — the token is valid but its external_id doesn’t match the {product_id} in the URL (a key for product A can’t read product B).

📦 The response

The envelope, with actions ordered oldest → newest:

{
  "product_id": "YOUR_PRODUCT_ID",
  "user_id": "user_12345",
  "count": 3,
  "as_of": 1736940750.881,
  "actions": [
    {
      "type": "pageview",
      "title": "Page Load: Dashboard",
      "description": "User landed on the dashboard page",
      "timestamp_start": 1736940685.103,
      "timestamp_end": 1736940691.250,
      "raw_url": "https://app.example.com/dashboard",
      "canonical_url": "https://app.example.com/dashboard",
      "index": 0
    },
    {
      "type": "click",
      "title": "Click Export Csv",
      "description": "User clicked the Export Csv button on the dashboard page",
      "timestamp_start": 1736940691.250,
      "timestamp_end": 1736940705.610,
      "raw_url": "https://app.example.com/orders/12345",
      "canonical_url": "https://app.example.com/orders/:id",
      "index": 1
    },
    {
      "type": "submit",
      "title": "Submit Payment Form",
      "description": "User submitted the Payment form on the checkout page",
      "timestamp_start": 1736940705.610,
      "timestamp_end": 1736940705.610,
      "raw_url": "https://app.example.com/checkout",
      "canonical_url": "https://app.example.com/checkout",
      "index": 2
    }
  ]
}

Each action carries type, title, description, timestamp_start, timestamp_end, raw_url, canonical_url, and index. The user_id lives on the envelope, not inside each action.

Test it from your terminal before wiring anything. Use a real product id, a user_id you’ve actually identified, and your mcp_key:

curl "https://mcp.autoplay.ai/users/YOUR_PRODUCT_ID/user_12345/live-activity?limit=10" \
  -H "Authorization: Bearer YOUR_MCP_KEY"

A 200 with a populated actions array means the endpoint is working and the user has footsteps on file.

🚫 What this endpoint does not give you

Activity is the only surface with a REST fallback. Everything else is MCP-only:

Capability	Where it lives
Onboarding progress and journey stage	`get_onboarding_context`
The combined recommendation read	`get_recommendation_context`
Whether the agent may interrupt	`get_proactivity_criteria`
Launching the next step or a chosen tour	`guide_next_step`, `trigger_user_tour`
Recording a confirmed completion	`record_workflow_confirmation`

If you need any of those, connect over MCP.

⏳ Before activity appears

This endpoint returns something only once Autoplay has recorded activity for that user — your activity source must be wired up and the user must have generated events. With PostHog (the source used in the Quickstart): complete Quickstart Steps 1–3 — the snippet, posthog.identify(...), product registration, and the ingest webhook. Other sources (e.g. Amplitude) follow the same idea through their own ingestion path.

Identifying a user alone stores nothing. With PostHog, activity is built only from $pageview and $autocapture events (page loads, clicks, form submits) — a user who has identified but not yet browsed returns an empty actions array. Other sources capture their own equivalent events. Make sure capture is enabled and the user has actually navigated or clicked before expecting results.

Retention — this is short-lived “live” memory, not an archive:

4-hour TTL (ACTIVITY_TTL_S = 14400) — older activity expires.
50 actions max per user (ACTIVITY_MAX_EVENTS = 50) — older ones are trimmed.

Who We Are

Get Started

Live User Activity

AI Support Agents

Visual User Tours

Autoplay MCP

Reference

🌐 The endpoint

📦 The response

🚫 What this endpoint does not give you

⏳ Before activity appears

​🌐 The endpoint

​📦 The response

​🚫 What this endpoint does not give you

​⏳ Before activity appears

🌐 The endpoint

📦 The response

🚫 What this endpoint does not give you

⏳ Before activity appears