edgeapiCacheHuddlesList

Seen 2 time(s) in 1 run(s).

What it sent and what came back (the newest 2 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261103T065639_mattSlack, step 4: goto /client: 200, 516 ms

Sent:

{
  "query": {
    "_x_app_name": "client",
    "fp": "6f",
    "_x_num_retries": "0"
  },
  "body": "{\"token\":\"xoxc-12165421006739-12156263517591-12492529441700-5bffe6e6a317b9bbab53d938a4526d20e882de6ab372cd46f9f90868bb0322a0\"}"
}

Answered:

{
  "huddles": [],
  "ok": true
}

runs/inspect/20261103T065639_mattSlack, step 6: goto /client/T0C4VCD06MR/D0C8VAE7REU: 200, 57 ms

Sent:

{
  "query": {
    "_x_app_name": "client",
    "fp": "6f",
    "_x_num_retries": "0"
  },
  "body": "{\"token\":\"xoxc-12165421006739-12156263517591-12492529441700-5bffe6e6a317b9bbab53d938a4526d20e882de6ab372cd46f9f90868bb0322a0\"}"
}

Answered:

{
  "huddles": [],
  "ok": true
}

What it does

Asks Slack's edge cache for the list of huddles running in the workspace: it sent only the token and answered huddles: [], ok: true, once on step 4 goto /client (516 ms) and once on step 6 goto the DM (57 ms).

What our machine does with it

Nothing: no log-cli code calls it. The engine (python/slackApi/engine.py, actions ping, workspaces, chats, read, send, watch over vendor/gabrielSlack) never uses this endpoint; it is Slack's web client's own traffic, seen only because the log inspect AdsPower run on mattSlack loaded the page.

What can go wrong

Both calls were 200. If it answered ok: false the client would simply show no huddles; nothing of ours reads it.