PlatformsDiscordBackground

discordApiUsersMeNotes

Domainbackground
Kindendpoint
doc_id—
Pathdiscord.com/api/users/@me/notes
Sends—
Readsmessage, code
Called fromruns/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
reaev_065e7ad37dcb5911d240f9de7d6e2882220c5a8d7c025d92b46a23de59cf297c

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

ActionOur stepTimesStatusTookAfter step startErrors
inspectstep 31: wait 60s1404354 ms241900 ms—

What it sent and what came back (the newest 1 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/20261028T062914_sourcedandsoldtothehighestbidder, step 31: wait 60s: 404, 354 ms

Sent:

null

Answered:

{
  "message": "Unknown User",
  "code": 10013
}

What it does

Reads the private note the account keeps on a user (.../notes/<user_id>).

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

404 means there is no note on that user: normal, not an error.