discordApiAuthConditionalStart
| Domain | background |
| Kind | endpoint |
| doc_id | — |
| Path | discord.com/api/auth/conditional/start |
| Sends | — |
| Reads | challenge, ticket |
| 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 3: goto /login | 1 | 200 | 432 ms | 5774 ms | — |
| inspect | step 1: goto /channels/@me | 1 | 200 | 299 ms | 12301 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: 200, 299 ms
Sent:
nullAnswered:
{
"challenge": "{\"publicKey\":{\"challenge\":\"We7-A9RvlUdIVrsvAOjVuQ18ey5TGKFs895TLbjWqhs\",\"timeout\":300000,\"rpId\":\"discord.com\",\"allowCredentials\":[],\"userVerification\":\"required\",\"extensions\":{\"uvm\":true}},\"mediation\":\"conditional\"}",
"ticket": "f63d9936-74a3-482a-b441-9fd5fd8c4782"
}runs/inspect/20261028T062914_sourcedandsoldtothehighestbidder, step 3: goto /login: 200, 432 ms
Sent:
nullAnswered:
{
"challenge": "{\"publicKey\":{\"challenge\":\"uAUvFkCei5fkBkGVVT5WFupqaUa3DLocQ8shWXI7sIA\",\"timeout\":300000,\"rpId\":\"discord.com\",\"allowCredentials\":[],\"userVerification\":\"required\",\"extensions\":{\"uvm\":true}},\"mediation\":\"conditional\"}",
"ticket": "8aecfcc2-4ff4-45cc-bedb-24245f34b530"
}What it does
Starts the login page's conditional sign-in (passkey autofill): the server hands back a challenge the browser could answer with a saved passkey.
What our machine does with it
Not used: matt signs in himself (matt, 2026-10-28), so our step only records it.
What can go wrong
If it fails the page still shows the email and password form, so sign-in goes on the normal way.