TCGPlayer Setup Guide

Time: 15 minutes | Difficulty: Moderate | Market: Collectibles Mode: Full automation (conditional) | API: Developer API (REST) | Docs: developer.tcgplayer.com

This guide wires a TCGPlayer bot to the Developer API using the botwir3 runtime. Configure API credentials, connect to card pricing and catalog data, and run automated seller-side strategies locally.

⚠ Access requirements

TCGPlayer requires API approval before access is granted. This may include:

• Registering a developer application at developer.tcgplayer.com
• Approval of the application (timeline varies)
• Agreement to the TCGPlayer API Terms of Use
• Restrictions on competitive use and commercial redistribution of data
• Buyer-side automated purchasing terms are ambiguous — verify current developer terms before deploying any buyer-side automation

TCGPlayer API Terms of Use | TCGPlayer Developer Portal

The user is responsible for obtaining appropriate access and complying with all platform terms.

Before you start

Verify that automated operation is permitted under TCGPlayer's current terms of service before deploying. botwir3 provides tools for building structured automation. The user is responsible for compliance with the platform's terms and all applicable regulations.

⚠ Buyer-side automation. TCGPlayer's API terms are clear on seller-side operations (inventory, pricing, catalog data). Buyer-side automated purchasing is not clearly addressed in the current terms. Verify with TCGPlayer's developer team before deploying buyer-side automation.

TCGPlayer Terms of Service | Last verified: May 2026 (ToS dated September 27, 2023; API Terms dated June 8, 2022)

What you need

• A TCGPlayer seller account (for seller-side automation) or a standard account
• API access approved through the developer portal
• The botwir3 runtime downloaded and unzipped
• A strategy config file from the builder

Step 1: Create API credentials

1. Apply for API access at developer.tcgplayer.com
2. Once approved, note the Application ID and Bearer Token (or client credentials for OAuth)
3. Review the API Terms of Use — note restrictions on data redistribution and competitive use

Permissions required: API access granted through application approval. Permissions to disable: N/A. The API does not support fund withdrawal or payment operations.

🔒 Security. TCGPlayer API tokens grant access to catalog, pricing, and seller inventory endpoints. No payment or withdrawal operations are available through the API. Tokens are stored in a local config file and are not transmitted to botwir3 or any third party. botwir3 never sees, stores, or has access to platform credentials.

Step 2: Configure the adapter

Create adapter.json in the bot directory:

{
  "adapter": "tcgplayer",
  "credentials": {
    "bearer_token": "paste-bearer-token-here"
  },
  "product_line": "magic",
  "mode": "seller",
  "environment": "live",
  "rate_limit_ms": 1000
}

product_line: "magic" (Magic: The Gathering), "pokemon" (Pokémon), "yugioh" (Yu-Gi-Oh!), "lorcana" (Disney Lorcana), etc. TCGPlayer supports multiple collectible card games.

mode: "seller" for inventory and repricing operations. Buyer-side automation is subject to the access requirements noted above.

API keys are stored in a local config file on the machine running the bot. They are not transmitted to botwir3 or any third party. botwir3 never sees, stores, or has access to platform credentials.

Step 3: Test the connection

botwir3 test --adapter tcgplayer

Expected output:

[botwir3] Adapter: tcgplayer
[botwir3] Connection: OK
[botwir3] Permissions: catalog, pricing, seller_inventory
[botwir3] Rate limit: per API documentation

Step 4: Start the bot

botwir3 start --config my-strategy.json

The runtime loads the strategy, computes the spec hash, connects to TCGPlayer via the local API token, and begins evaluating signals. The gate function compares proposed actions against the configured spec. The user is responsible for monitoring the bot and verifying execution outcomes.

Rate limits and considerations

ℹ API restrictions. TCGPlayer API terms prohibit using data for competitive purposes, combining with other pricing sources for redistribution, or commercial redistribution of catalog data. The bot processes data locally — no data is shared or redistributed.

Common TCGPlayer bot configurations include automated repricing (adjusting seller listings based on market price movements), inventory monitoring (tracking price changes on cards in a collection), and arbitrage signal generation (identifying cards priced below market value across sellers). All actions and decisions are recorded in the local ledger.

Troubleshooting

Related guides

• Shopify Setup Guide — e-commerce, seller-side automation
• Amazon Seller Setup Guide — e-commerce, seller-side automation
• CS2 Markets Setup Guide — collectibles, third-party market APIs

One bot. $129. No subscription. No $749/mo platform. → Build for TCGPlayer