Automate Microsoft Rewards QR Redemption
Budget: $30 – $250 USD
The goal is to turn the manual “QR-code” redemption flow inside Microsoft Rewards into a fully automated back-end process.
Flow to replicate
1. Authenticate to Microsoft Rewards with stored email / password.
2. Navigate to the Redeem page, choose the desired reward, and pick the “QR code” redemption option (skip the mobile-number path).
3. Capture the QR code that appears, extract the login URL it encodes, and hit that endpoint directly—no physical scan.
4. The Rewards site then shows a random six-digit code. Pass that code to the Bing app’s verification end-point so the redemption completes.
5. Return success / failure so the calling service can proceed.
What I need built from scratch
• A clean script, micro-service, or library—language is flexible—that carries out the entire sequence over HTTPS calls.
• Handling of Microsoft’s multi-factor authentication is essential; assume it may appear at any stage.
• The solution may employ any suitable public or private API; there’s no constraint as long as it’s reliable.
• Well-commented code plus brief documentation describing dependencies, usage, and how to refresh tokens/cookies as they expire.
• A simple demo run that shows one redemption executed end-to-end.
Acceptance criteria
• No manual steps: the QR image never needs to be scanned by a camera.
• Redemption succeeds for at least one live account during testing.
• Source code passes a quick security review (no hard-coded secrets, proper error handling).
Mention of budget is not necessary; focus is on a robust, testable automation.
Flow to replicate
1. Authenticate to Microsoft Rewards with stored email / password.
2. Navigate to the Redeem page, choose the desired reward, and pick the “QR code” redemption option (skip the mobile-number path).
3. Capture the QR code that appears, extract the login URL it encodes, and hit that endpoint directly—no physical scan.
4. The Rewards site then shows a random six-digit code. Pass that code to the Bing app’s verification end-point so the redemption completes.
5. Return success / failure so the calling service can proceed.
What I need built from scratch
• A clean script, micro-service, or library—language is flexible—that carries out the entire sequence over HTTPS calls.
• Handling of Microsoft’s multi-factor authentication is essential; assume it may appear at any stage.
• The solution may employ any suitable public or private API; there’s no constraint as long as it’s reliable.
• Well-commented code plus brief documentation describing dependencies, usage, and how to refresh tokens/cookies as they expire.
• A simple demo run that shows one redemption executed end-to-end.
Acceptance criteria
• No manual steps: the QR image never needs to be scanned by a camera.
• Redemption succeeds for at least one live account during testing.
• Source code passes a quick security review (no hard-coded secrets, proper error handling).
Mention of budget is not necessary; focus is on a robust, testable automation.
Related categories:
JavaScript
Python
C# Programming
Node.js
OAuth
Scripting
Security
Automation
API Development
Microservices