Developer Documentation
TCG API documentation
REST endpoint references, authentication examples, response formats, and implementation notes for trading card data, SKU prices, live listings, sales history, CSV exports, card recognition, and PSA lookup.
API Documentation
Comprehensive guides and API reference for TCG APIs
Downloads a build-ready markdown version with INSERT_YOUR_API_KEY_HERE placeholders.
Introduction
Welcome to the TCG APIs documentation. This API provides access to trading card game data, including games, expansions, cards, and pricing information. Use this documentation to learn how to authenticate, make requests, and handle responses.
No External API Keys Required
Our service does not require you to have a TCGPlayer API key. We handle all the data collection for you, making it easier to access trading card game data.
Base URL
https://api.tcgapis.com/api/v1Getting Started
To get started with the TCG APIs, you'll need:
- An API key (available in your dashboard)
- Understanding of REST API principles
- A tool to make HTTP requests (like cURL, Postman, or your programming language of choice)
API Features
- Comprehensive trading card game data
- User profile and usage statistics
- Game, expansion, and card information
- JSON-formatted responses
- RESTful API design
- Paginated list endpoints (default 25 results per page)
Pagination
All endpoints that return lists of results support pagination via query parameters:
limit— Number of results to return per request (default: 25, max: 100)offset— Number of results to skip (default: 0)
Paginated responses include count (results in this page), total (total available), offset, and limit fields. To iterate through all results, increment the offset by the limit value:
# First page GET /api/v2/cards/23551?limit=25&offset=0 # Second page GET /api/v2/cards/23551?limit=25&offset=25 # Third page GET /api/v2/cards/23551?limit=25&offset=50