discordApiUsersMe


Domain	background
Kind	endpoint
doc_id	—
Path	`discord.com/api/users/@me`
Sends	—
Reads	`message`, `code`, `id`, `username`, `avatar`, `discriminator`, `public_flags`, `flags`, `banner`, `accent_color`, `global_name`, `avatar_decoration_data` and 25 more
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 2 time(s) in 2 run(s).

Action	Our step	Times	Status	Took	After step start	Errors
inspect	step 1: goto /login	1	200	380 ms	6569 ms	—
inspect	step 1: goto /channels/@me	1	401	1147 ms	10897 ms	—

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/20261030T222341_sourcedandsoldtothehighestbidder, step 1: goto /channels/@me: 401, 1147 ms

Sent:

null

Answered:

{
  "message": "401: Unauthorized",
  "code": 0
}

runs/inspect/20261028T074137_sourcedandsoldtothehighestbidder, step 1: goto /login: 200, 380 ms

Sent:

null

Answered:

{
  "id": "1434443116663930960",
  "username": "sourcedandsoldtothehighestbidder",
  "avatar": "82e338d2355f93220637a3ec394ca3c4",
  "discriminator": "0",
  "public_flags": 0,
  "flags": 0,
  "banner": null,
  "accent_color": null,
  "global_name": null,
  "avatar_decoration_data": null,
  "collectibles": null,
  "display_name_styles": null,
  "banner_color": null,
  "clan": {
    "identity_guild_id": null,
    "identity_enabled": false,
    "tag": null,
    "badge": null
  },
  "primary_guild": {
    "identity_guild_id": null,
    "identity_enabled": false,
    "tag": null,
    "badge": null
  },
  "mfa_enabled": false,
  "locale": "en-US",
  "premium_type": 0,
  "email": "matthewdonsemail@gmail.com",
  "verified": true,
  "phone": "+84586762027",
  "nsfw_allowed": true,
  "linked_users": [],
  "bio": "try out log on https://log.listeningkit.com\ntokenmaxxing on https://inferencesaver.com/en/",
  "authenticator_types": [],
  "age_verification_status": 4,
  "store_country": {
    "country": "VN",
    "set_at": null,
    "is_locked": false
  }
}

What it does

Reads the signed-in account itself (GET /api/v9/users/@me): its id, username, global name, whether its email is verified and whether two-step is on. The web client calls it as soon as the app loads.

What our machine does with it

It is the session check: log discord session check sends this one call through vendor/endcord with the account's saved token, and Discord's answer decides sessionState in Twenty (rule 73). 200 with the account is loggedIn.

What can go wrong

401 means the token is no longer valid (sessionDead: the account has to be signed in again in its browser), 403 a locked or disabled account, 429 rate limited (the governor backs off). endcord's own constructor exits on a 401; the engine catches that and answers sessionDead.

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

What it does

What our machine does with it

What can go wrong

On this page