ListeningKitdiscordApiQuestsGetDecisions
| Domain | background |
| Kind | endpoint |
| doc_id | — |
| Path | discord.com/api/quests/get-decisions |
| Sends | — |
| Reads | request_id, decisions |
| Called from | runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder/script1.js:208 app_store_parental_revocation, runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder/script1036.js:1 parse, runs/inspect/20261030T222341_sourcedandsoldtothehighestbidder/script1221.js:2 anonymous, runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder/script1245.js:2 anonymous |
| rea | ev_065e7ad37dcb5911d240f9de7d6e2882220c5a8d7c025d92b46a23de59cf297c |
Seen 6 time(s) in 4 run(s).
| Action | Our step | Times | Status | Took | After step start | Errors |
|---|---|---|---|---|---|---|
| inspect | step 1: goto /channels/@me/<id> | 1 | 200 | 450 ms | 14921 ms | — |
| inspect | step 5: click e40 | 1 | 200 | 362 ms | 16903 ms | — |
| inspect | step 9: goto /channels/@me | 1 | 200 | 692 ms | 15056 ms | — |
| inspect | step 25: goto /channels/@me | 1 | 200 | 523 ms | 15461 ms | — |
| inspect | step 1: goto /login | 1 | 200 | 395 ms | 24174 ms | — |
| inspect | step 2: snapshot | 1 | 200 | 508 ms | 53252 ms | — |
What it sent and what came back (the newest 3 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/20261030T222341_sourcedandsoldtothehighestbidder, step 2: snapshot: 200, 508 ms
Sent:
{
"query": {
"placement": "3",
"num_decisions_requested": "1",
"client_heartbeat_session_id": "89081172-35da-4e8d-8b5c-da5e1bf81773",
"client_ad_session_id": "a683df8e-3741-4919-9185-22ceb745e6fb"
},
"body": null
}Answered:
{
"request_id": "b5af6f95-b8d1-436e-bf9b-d90acf885631",
"decisions": []
}runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder, step 1: goto /login: 200, 395 ms
Sent:
{
"query": {
"placement": "3",
"num_decisions_requested": "1",
"client_heartbeat_session_id": "042a6464-5284-440e-831b-0ed816011058",
"client_ad_session_id": "8b8ce89d-11bc-4e79-b242-5c10647e14f5"
},
"body": null
}Answered:
{
"request_id": "a4703257-f42f-4dc3-ba6c-7eb5d028d04e",
"decisions": []
}runs/inspect/20261028T065202_sourcedandsoldtothehighestbidder, step 1: goto /channels/@me/<id>: 200, 450 ms
Sent:
{
"query": {
"placement": "3",
"num_decisions_requested": "1",
"client_heartbeat_session_id": "76647484-56eb-47e1-a676-e51ce70342ac",
"client_ad_session_id": "c139cbba-8718-4677-a6a8-4401494e07df"
},
"body": null
}Answered:
{
"request_id": "a5280851-3126-4788-8a5f-1d6052692aa7",
"decisions": []
}What it does
The batch version of the Quest decision, for several surfaces at once.
What our machine does with it
Nothing in log-cli waits for it or reads it. It is part of what Discord's client loads around the page; a watch or a send never depends on it.
What can go wrong
The account carries on whatever it answers; a failure here changes nothing for our steps.