umbrella_rs
Store modules

Premium Bandai

Configure and run registration, cart, timed-drop, and monitor modes.

Premium Bandai supports regions nz, au, sg, and us. Every task's PID must contain two values separated by a semicolon:

basepid;atcpid

basepid identifies the product for pages and monitoring; atcpid is the variant/item identifier used for add to cart.

Required setup

Every Bandai mode needs an Apicloak API key. Additional requirements are:

ModeAdditional settings/resources
registerHeroSMS key, profile, target Bandai account group, email list, IMAP config, phone country/max price/country code.
register-multi-regionEverything for register, plus Riskbypass keys.
cart-clearRiskbypass keys and a Bandai account.
drop-guestRiskbypass keys, supported checkout region, profile, account, optional start time.
monitor-guestRiskbypass keys, supported checkout region, profile, account.

All modes also require task proxies and a saved Bandai monitor configuration with monitor proxies.

Country behavior

  • Registration accepts nz, au, sg, or us.
  • Checkout modes currently have Global-e checkout data for New Zealand, Australia, and Singapore. A US drop-guest or monitor-guest task stops with an unsupported checkout-data error.
  • Australia requires the profile State / region to be an Australian state code such as NSW or its full name.

register

Creates one account in the selected country and saves it to the target Bandai account group. The phone fields mean:

  • HeroSMS country — numeric country identifier used by HeroSMS;
  • HeroSMS max price — optional maximum number price;
  • Bandai phone country — two-letter country code used in registration, for example GB.

The task draws an unused address from the selected email list and uses the selected IMAP config for email verification where required.

register-multi-region

Registers in the selected country, then reuses the resulting account in every other supported region. For each additional region it resets device data and cookies, creates a new session, logs in, and accepts that region's terms.

This mode needs Riskbypass keys in addition to the normal registration keys.

cart-clear

Logs into the selected Bandai account and clears its remote cart. Use this to remove stale items before a drop. PID and country are still required by the current task form even though the action is account-oriented.

drop-guest

Runs a timed checkout. Start time is optional:

  • when supplied, it waits for today's local HH:MM:SS;
  • when blank or already passed, it continues immediately;
  • it can also continue early if another Bandai drop task carts the same base PID.

Flow: create session → load cart details → wait → retry add to cart → log into the selected account → save cart checkout data → initialize checkout → get cart token → submit checkout → start payment.

Despite the mode name, the current checkout flow requires the selected Bandai account.

monitor-guest

Uses the same checkout flow as drop-guest, but waits for the shared Bandai monitor to mark the base PID live instead of waiting for a clock time.

The shared monitor uses the delay, replication, and proxy pool saved on the Monitors page.

Restarts

Bandai HTTP calls detect the module's shape-block response and request a clean task restart. These restarts do not count toward the five consecutive ordinary failure limit. Other operations use bounded internal attempts where provided by the module, then return an error to the main task engine.

On this page