π Add / activate authenticator (maFile, both steps)
Generates a Steam mobile authenticator (maFile) β the full lifecycle in ONE endpoint. The step is auto-detected from the parameters (or force it with step: 1/2).
STEP 1 (add) β send username + password. If the account uses email Steam Guard, the first call returns HTTP 200 { "state": "NEED_EMAIL_CODE", "loginsession": "...", "nextrequest": {...} }; read the emailed code and call again with emailcode + loginsession. On success you get the maFile + accesstoken and Steam sends an SMS.
STEP 2 (finalize) β send sharedsecret + accesstoken (both from step 1) + activationcode (the code Steam sent, by SMS or email). Alternatively send the whole mafile + activationcode (sharedsecret/accesstoken are then read from it). smscode and emailcode are accepted as aliases for activationcode. The presence of sharedsecret, a mafile, or an activation code selects this step.
Works with or without a phone number: with a phone Steam sends the activation code by SMS, otherwise by email. Set mafiledownload to true (step 1) to receive the maFile as a downloadable <steamid>.maFile. IMPORTANT: store the revocation_code β it cannot be recovered.
Request
- Base URL: https://www.steamwebapi.com
- URL: https://www.steamwebapi.com/steam/api/guard/add
- Auth: API key in query parameter key
Request body
Response
Add (login): AWAITING_FINALIZATION β the maFile (with fully_enrolled already set to true so the saved file is final-ready), accesstoken, a mafiledownloadlink (a stateless data: URI that downloads the maFile) and mafilefilename (the <steamid>.maFile name to use with an <a download>) β or NEED_EMAIL_CODE (loginsession). Finalize: confirmation that the mobile authenticator is now active. With mafiledownload=true: the maFile as a file attachment.
Changes
No recorded changes to this operation across all 1 revision of this API.