PlatformsDiscordBackground

discordApiUsersMeSavedMessages

Domainbackground
Kindendpoint
doc_id—
Pathdiscord.com/api/users/@me/saved-messages
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 6 time(s) in 4 run(s).

ActionOur stepTimesStatusTookAfter step startErrors
inspectstep 1: goto /channels/@me/<id>1404342 ms11824 ms—
inspectstep 5: click e401404367 ms12912 ms—
inspectstep 9: goto /channels/@me1404430 ms9553 ms—
inspectstep 25: goto /channels/@me1404353 ms8663 ms—
inspectstep 1: goto /login1404384 ms18497 ms—
inspectstep 2: snapshot1404454 ms51746 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: 404, 454 ms

Sent:

{
  "query": {
    "bookmark_ids": "true"
  },
  "body": null
}

Answered:

{
  "message": "Unknown Saved Messages",
  "code": 10133
}

runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder, step 1: goto /login: 404, 384 ms

Sent:

{
  "query": {
    "bookmark_ids": "true"
  },
  "body": null
}

Answered:

{
  "message": "Unknown Saved Messages",
  "code": 10133
}

runs/inspect/20261028T065202_sourcedandsoldtothehighestbidder, step 1: goto /channels/@me/<id>: 404, 342 ms

Sent:

{
  "query": {
    "bookmark_ids": "true"
  },
  "body": null
}

Answered:

{
  "message": "Unknown Saved Messages",
  "code": 10133
}

What it does

Reads the account's saved (bookmarked) messages.

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 the feature isn't on for this account: normal.