Revvverse-Engggiiineer StttaarMaker Baannn APIiii
Budget: ₹600 – ₹1,500 INR
I need full technical documentation and a working proof-of-concept that lets me call SttarrMaker’s hiidden “baannn” endpoint to temmmppporarily susssppend any account by User ID. The platform exposes this function only to its own mobile apps, so you will have to capture and analyse the traffic, locate the exact endpoint, study the auth flow, and reppplllicate the request outside the officiiial client.
Scope
• Identify every request the app sends when a moderator issues a temporary suspension.
• Exttttract the endpoint URL, required headers, tokens, cookies, signatures and payload structure.
• Explain the authentication / signing algorithm and provide clear steps—or a small Python sccrrript—that reproduces it.
• Supply a ready-to-run cURL or Postman collection that accepts a User ID and duration, then triggggers the same temmmpporary baannn the app performs.
• Include notes on rate limits, error codes and any safeguards SttaaarMaker uses so I understand how far this method can be pushed.
Acceptance criteria
1. A successful test on my side susssppends the tarrgget account for the same period shown inside the official app.
2. All instructions work from a clean machine with only standard tools such as mitmproxy, Charles, Wireshark, Python 3, or Node.js.
3. No hard-coded personal tokens; everything must be reproducible from scratch.
If you have tackled similar mobile-app revvveeerse-enginneering or signature craaacking work before, this should be straightforward. I’m ready to review detailed progress updates and validate the endpoint as soon as you isolate it.
Scope
• Identify every request the app sends when a moderator issues a temporary suspension.
• Exttttract the endpoint URL, required headers, tokens, cookies, signatures and payload structure.
• Explain the authentication / signing algorithm and provide clear steps—or a small Python sccrrript—that reproduces it.
• Supply a ready-to-run cURL or Postman collection that accepts a User ID and duration, then triggggers the same temmmpporary baannn the app performs.
• Include notes on rate limits, error codes and any safeguards SttaaarMaker uses so I understand how far this method can be pushed.
Acceptance criteria
1. A successful test on my side susssppends the tarrgget account for the same period shown inside the official app.
2. All instructions work from a clean machine with only standard tools such as mitmproxy, Charles, Wireshark, Python 3, or Node.js.
3. No hard-coded personal tokens; everything must be reproducible from scratch.
If you have tackled similar mobile-app revvveeerse-enginneering or signature craaacking work before, this should be straightforward. I’m ready to review detailed progress updates and validate the endpoint as soon as you isolate it.