Buyer Activity

​

Overview

• Calls show each admitted buyer API request, including reads, failures, denials, latency, workload identity, and correlation IDs.
• Changes show meaningful CREATE, UPDATE, DELETE, ARCHIVE, and EXECUTE mutations on advertisers, campaigns, creatives, media buys, products, and packages.

• Compliance — review the recorded trail of who changed what and when across multi-tenant workspaces.
• Debugging — reconstruct the sequence of events around a campaign that suddenly stopped pacing or a creative that flipped to rejected.
• Post-incident analysis — answer “what changed in the last hour?” and “did this agent touch anything it wasn’t supposed to?”.
• Operational visibility — feed the data into a SIEM, a Slack channel, or your own dashboard.

​

Open Activity in your agent client

{
  "name": "list_buyer_activity",
  "arguments": {
    "view": "calls",
    "outcome": "failed",
    "surface": "mcp"
  }
}

• Calls — normalized REST, MCP, and A2A operations with workload, outcome, latency, environment, and correlation IDs;
• Call detail — recorded request fields and available response or error details, redacted allowlisted headers, validation/response steps, timing, and retry guidance;
• Ask Murph about this call — calls the shared typed ask_murph tool with the exact activityUid and renders the evidence-grounded diagnosis inline, without adding a chat turn; and
• Changes — the compatible domain-mutation history previously shown as the entire Activity log.

​

Prerequisites

• A Scope3 API key (see Authentication)
• Buyer members can list account-scoped call and change metadata. Account or advertiser admins can open redacted call detail. Service tokens can see only activity attributed to their stable workload lineage.
• Optional: a campaign or advertiser ID to scope the feed

export SCOPE3_API_KEY=scope3_<your_api_key>
export BASE=https://api.interchange.io/api/v2/buyer
export API_BASE=https://api.interchange.io/api/v2

​

Step 1: List recent activity

curl "$BASE/audit-logs?take=50" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

{
  "data": {
    "logs": [
      {
        "id": 81234,
        "timestamp": "2026-04-26T14:30:12.481Z",
        "createdAt": "2026-04-26T14:30:12.481Z",
        "action": "UPDATE",
        "resourceType": "CAMPAIGN",
        "resourceId": "camp_abc123",
        "resourceName": "Q2 Brand Launch",
        "parentType": "BRAND_AGENT",
        "advertiserId": 42,
        "userId": 901,
        "userEmail": "alex@brand.example",
        "userName": "Alex Operator",
        "serviceTokenId": null,
        "serviceTokenName": null,
        "parameters": { "budget": { "total": 250000 } },
        "changes": { "budget.total": { "from": 200000, "to": 250000 } },
        "description": "Increased total budget from $200,000 to $250,000"
      }
    ],
    "total": 4128
  },
  "meta": {
    "pagination": { "skip": 0, "take": 50, "total": 4128, "returned": 1 }
  }
}

​

Step 2: Filter

curl "$BASE/audit-logs?startDate=2026-04-26T00:00:00Z&endDate=2026-04-26T23:59:59Z&take=200" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

curl "$BASE/audit-logs?advertiserId=42&startDate=2026-04-25T14:30:00Z" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

curl "$BASE/audit-logs?resourceTypes=CREATIVE,MEDIA_BUY&take=100" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

​

Step 3: Common patterns

​

Who changed this campaign?

curl "$BASE/audit-logs?campaignId=camp_abc123&take=100" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

​

What did this agent do today?

curl "$BASE/audit-logs?startDate=2026-04-26T00:00:00Z&take=500" \
  -H "Authorization: Bearer $SCOPE3_API_KEY" \
  | jq '.data.logs[] | select(.serviceTokenName == "ops-bot")'

​

Did this incident leave a trace?

curl "$BASE/audit-logs?startDate=2026-04-26T13:45:00Z&endDate=2026-04-26T14:15:00Z&resourceTypes=CAMPAIGN,MEDIA_BUY" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

​

Debug API calls

curl "$API_BASE/activity/calls?startTime=2026-07-13T00:00:00Z&outcome=failed" \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

• activityUid, requestId, and traceId for support and tracing;
• the normalized operation, protocol, HTTP status, outcome, and latency;
• operationDispatches, a bounded server-observed record of buyer or storefront facade operations selected by a v3 tool, in invocation order;
• the stable workloadUid and credential snapshot used for that request;
• an explicit runUid when the caller supplied a run ID or eligible W3C trace, plus its clientRunId correlation identifier when supplied;
• the apiVersion observed by the server for the routed request;
• a safe error class, fault domain, and retry disposition when the call failed.

• redactedInput: schema-declared MCP arguments, or schema-validated REST path, query, and body fields, after sensitive values are removed;
• redactedOutput: the redacted typed MCP result, or the public REST error envelope returned to the caller (successful REST payloads are not copied into the ledger);
• safeHeaders: an explicit allowlist of non-secret debugging headers, such as content type, idempotency key, user agent, request ID, and run ID;
• steps: validation and response milestones, including field paths and public validation messages; and
• route, timing, workload, run, trace, and retry guidance.

​

Group calls into an agent run

{
  "jsonrpc": "2.0",
  "id": 42,
  "method": "tools/call",
  "params": {
    "name": "api_call",
    "arguments": { "operation": "campaigns.list" },
    "_meta": {
      "scope3/run-id": "nightly-reporting:2026-07-14",
      "scope3/run-label": "Nightly reporting"
    }
  }
}

{
  "_meta": {
    "scope3/activity": {
      "activityUid": "e691bf1a-2f17-4eec-9394-e647dcfe994d",
      "requestId": "0c240930-4e42-4a7f-8716-7329c862932f",
      "traceId": "4bf92f3577b34da6a3ce929d0e0e4736",
      "runUid": "421ea561-69fc-46ee-93c3-b8e2676ef603"
    }
  }
}

curl "$BASE/campaigns" \
  -H "Authorization: Bearer $SCOPE3_API_KEY" \
  -H "X-Scope3-Run-Id: nightly-reporting:2026-07-13" \
  -H "X-Scope3-Run-Label: Nightly reporting"

​

Best practices

• Retention — safe call diagnostics are retained for 90 days and slim call metadata for 13 months. Archive records you need longer to your own warehouse.
• Pagination ceiling — take is capped at 500. For larger exports, iterate by time window.
• Idempotency — id is stable per row, so client-side dedupe on id is safe across overlapping polls.
• Don’t rely on actions filtering at the API — the activity feed always restricts to meaningful actions; filter further client-side if you need to (e.g. only DELETE).

​

Endpoint reference

​

Related

• Notifications — push notifications for the same underlying events
• Errors — error codes you may see surfaced in parameters
• Authentication — required role and token setup