Control panel

A bot can’t message anyone first. Each person opens the bot and presses Start, then find lists them. Groups and channels work too — add the bot, then use its negative id.

Bot token @BotFather ↗ 👁

Prices are per dark store. A pincode, an area, or “Area, City” — changing it re-resolves the store.

Area or pincode save

A dry run does everything except send — useful while you dial in thresholds.

Pause overnight

Manual checks and dry runs always run — the pause is for the poller only.

Re-minting drops the cached WAF token and store pin. Forgetting history lets every live deal alert again.

Fetch mode how calls leave the machine Auto — HTTP, falling back to the browser HTTP only — one second a poll, needs a trusted IP Browser only — slow, survives a strict WAF

The fast path hands the browser's token to a plain HTTP client, whose TLS fingerprint does not match Chromium's. A strict WAF notices and answers 202 on a token it just issued. Browser mode keeps every call inside the page that solved the challenge — about 5s a pass instead of 1s.

Proxy routes the browser bootstrap and the polls

The WAF ties the token to the IP that solved the challenge, so on a rotating residential proxy an exit that changes between the challenge and the next call invalidates it every time. Write {session} into the username where your provider's sticky-session id goes and a fresh one is filled in for every token — same exit for the challenge, the reload and the polls, and a different exit each time one is refused.

DataImpulse user__cr.in;sessid.{session};sessttl.30 · Bright Data brd-customer-…-session-{session} · Oxylabs customer-…-sessid-{session}-sesstime-30

Bump the build version if Swiggy starts rejecting the calls — it mirrors their deployed web build. Saving it clears the pinned session so the next call goes out with the new header.

Set outside this panel, in the environment: