Skip to main content
Moving an existing inventory means splitting it across vaults and pushing it in batches. A vault holds 1,000 keys and a single import takes 300, so plan on making several passes.

What you need first

  • Your keys as plain text, one per line.
  • A decision on key type per vault. A vault holds either Steam keys or custom codes, so keep the two kinds in separate vaults. You can correct the type later from the vault’s About tab.
  • For Steam keys, which variant you generated them as in Steamworks.
  • An access key, if you are pushing them over the API.

The playbook

1

Split the inventory

Cut the pile into slices that fit one vault on your plan, between 250 and 1,800 keys.
Cut along a line that means something to you (per platform, per recruitment wave, per key variant) rather than splitting arbitrarily at the cap.
2

Create a vault per slice

Go to Vault in the sidebar and click Create key vault for each slice.
Make them custom vaults. Custom vaults are reusable across playtests and can carry their own redeem link. A system vault created inside a playtest’s Keys tab does neither.

Key vaults

System vaults, custom vaults, and how each one hands out keys.

Key distribution

The system vault a playtest builds for itself, and its limits.
3

Push the keys in, 300 at a time

Load each vault in batches.
On the vault’s Keys tab, click Add keys and choose Paste keys, Import from CSV, or Import from key vaults.
Keys already in the vault are skipped, so a partial re-run costs nothing.

Key vaults

Every vault command, argument, and flag.

Automate with the API

Playbook: authentication, pagination, and what the API will not do.
4

Point each vault at something

A stocked vault does not hand out anything on its own. Pick a route per vault.
Turn on Key Distribution on a playtest’s Config tab and point it at the vault.

Redeem links

Publishing, distributing, and resetting the link.

Give keys away with a redeem link

Playbook: gate the link and watch the inventory drain.

Moving keys between Userplay vaults

Keys already inside a Userplay vault do not need re-pasting. This is the only thing import means in this API: it copies from another vault. It does not accept a file.
Both vaults must hold the same key type. Use --scope to copy everything, only the available keys, or only the unredeemed ones.

How you know it worked

  • The vault’s Keys tab lists the count you loaded, with every key badged Available.
  • Re-running a batch leaves the total unchanged, and reports how many were skipped.
  • Once a playtest or a redeem link starts handing them out, keys flip to Assigned, then to Redeemed when a recipient actually reveals one.

Stock a key vault

Choosing the key type, the Steam variant, and the redeem scope.

Keys

Every key type, variant, and status.

Migrate your players

The same exercise for your tester list.

Hand out game keys

Playbook: point a playtest at the vault you just stocked.