TWT Accept

X (Twitter) cookie intake. You send an archive or a token list - every account is checked automatically (validity, followers, verified) through private proxies, and the payout amount is assigned per upload.

How it works

Send a file: .zip / .rar / .7z (cookie archive) or .txt / .json (auth_token list).
All auth_token values are extracted (nested archives included); duplicates are dropped.
Each account is checked through a proxy: is the token alive? status? how many followers?
Dead accounts are dropped; valid ones are grouped into follower buckets (visible in the job response).
Valid accounts accumulate in your open submission until the admin evaluates it.
The admin sets the payout amount manually; you see it once the payout is confirmed.

Payout

payouts are made in ETH only, to the wallet linked to your partner account. Set it once via POST /api/wallet or in the TG bot (/wallet 0x...);
accounts accumulate: while the admin has not evaluated your current submission, every new upload is added to the same open submission - you do not need to send everything at once;
once the admin sets the amount, the submission is closed for new accounts and the next upload starts a fresh one;
the amount is assigned manually by the admin per submission - there are no fixed rates;
the amount becomes visible to you (payout.amount, paid) only after the payout is confirmed;
valid (alive token) and locked (alive token, temporarily rate-locked) - both count as accepted;
dead (banned / invalid token) - not paid. Tokens that were already checked and found dead are recognized and rejected without re-checking (known_dead in the response) - do not resend them;
duplicates - not paid, both token-level (already sent by you or another partner) and account-level: the same X account supplied under different tokens is counted and paid once.

Authorization

Every request needs the header X-Api-Key: <your key>. The key is issued by the admin.

File upload

POST http://zweirad-handel.com/api/upload - multipart/form-data: file (required), password (archive password, if any), comment (optional label). Limit: 1024 MB.

curl -sS -X POST http://zweirad-handel.com/api/upload \
  -H "X-Api-Key: YOUR_KEY" \
  -F "[email protected]" \
  -F "password=1234"

Sending a token list

POST http://zweirad-handel.com/api/tokens - JSON:

curl -sS -X POST http://zweirad-handel.com/api/tokens \
  -H "X-Api-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tokens":["a1f...40hex","b2e...40hex"]}'

Setting your payout wallet

curl -sS -X POST http://zweirad-handel.com/api/wallet \
  -H "X-Api-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"wallet":"0x71C7656EC7ab88b098defB751B7401B5f6d8976F"}'

Job status

GET /api/job/<job_id> - returns the check progress, the follower buckets, the dead count and the submission this upload belongs to:

{
  "id": "up_ab12cd34ef56",
  "status": "done",
  "received": 10000, "new": 9980, "dupes": 20,
  "counts": {"0-50": 3000, "50-100": 1500, "100-1k": 4000},
  "dead": 1480, "locked": 3,
  "payout": {"id": "pay_...", "accounts": 8520, "uploads": 3,
             "status": "pending", "amount": null}
}

Job statuses: queued -> checking -> done. no_proxies - proxies are temporarily unavailable, retry later. amount stays null until the payout is confirmed.

History

GET /api/jobs - your last 20 uploads;
GET /api/payouts - your payouts (amounts and statuses) and your wallet;
POST /api/wallet - set your ETH payout wallet.

Errors

401 - missing or wrong key;
400 - no auth_token found / empty list;
413 - file over the limit.

TWT Accept - payout questions to the admin in Telegram.