User Guide — Get OAuth
About this tool
Use Get OAuth to request a new Microsoft OAuth refresh token or exchange an existing refresh token. Results appear separately in SUCCESS and ERROR. Microsoft may require verification or renewed consent.
1. Prepare your input
Paste one account per line, without a header. Blank lines are ignored. Use one separator consistently within each row. Field values must not contain the chosen separator; quoted CSV fields are not parsed. The recovery email is optional and must contain @. Use the accepted field orders below.
Accepted account formats
email|password
email|password|recovery_email
email|password|refresh_token|client_id
email|password|recovery_email|refresh_token|client_idField definitions
email: the Microsoft account address. password: the account password field. recovery_email: an optional recovery address, placed immediately after the password. refresh_token: the existing OAuth refresh token. client_id: the application client ID associated with that token; use a valid Microsoft application ID. Do not substitute an access token for a refresh token.
Separator details
Token tools accept pipe (|), comma (,), semicolon (;) or colon (:) separators. The first separator found determines how the row is split. The examples use pipes; substitute one supported separator consistently. One trailing separator is optional. Rows with missing or extra fields are skipped. A refresh token and client ID must be supplied together.
Example placeholders — replace before running
user@example.com|YOUR_PASSWORD|recovery@example.net2. Enter your API key
Enter a valid MailOld API key with sufficient quota. Double-click the key field to show or hide it. The browser saves the key when you leave the field; clear it and leave the field to remove the saved value. Keep the key and account data private.
3. Choose a connection
New token requests use Proxy. Rows containing an existing refresh token and client ID use the separate direct refresh flow automatically. An empty private list requests shared proxies only if your API key permits them.
Accepted proxy formats — one per line
ip:port
ip:port:username:passwordProxy notes
Use a reachable proxy with the correct credentials. Do not add a URL scheme, comments or extra separators. Private proxies are checked before processing; unavailable proxies are excluded. Shared proxy availability and access depend on your API key.
4. Start and review results
Click GET TOKEN or START. Watch the success and error counts. SUCCESS contains email, password, optional recovery email, the returned refresh token and client ID. Select Pipe or Comma for the output. Download .txt exports the corresponding result box. Stop prevents further queued work; active requests may finish.
Troubleshooting
Check field order, token/client ID pairing, API key quota and proxy connectivity. A revoked or expired refresh token can require signing in again through Microsoft. Complete Microsoft verification or consent on the official Microsoft page. If the service is busy, wait before retrying. Avoid repeatedly submitting the same failing account.
Protect your data
The browser can retain accounts, API keys, proxies and connection settings. Results and downloads may contain passwords and tokens. Use a trusted device, restrict access to exported files, and clear site data when finished on a shared device. See Privacy Policy for server processing details.