The Internet Game Database (IGDB) operates as a crowd-sourced and professionally maintained digital library containing metadata, release schedules, and historical records for thousands of video games. Acquired by Twitch, it functions both as a consumer discovery platform and as a robust developer resource through its public API. Understanding how this database structures its records and how developers utilize its API helps teams build better gaming applications.
Whether you want to track release calendars, research indie titles, or pull live metadata into a custom software project, IGDB provides structured endpoints to handle complex queries. This guide breaks down its core ecosystem, API authentication setup, query syntax, and practical integration steps.
Core Architecture and Community Moderation
IGDB relies on a hybrid model where registered users contribute information, and moderators verify submissions to maintain data accuracy. Every title entry aggregates essential identifiers across multiple platforms.
- Metadata Points: Titles span original releases, remasters, ports, and spin-offs, complete with release dates broken down by region and platform.
- Taxonomy & Classification: Games are tagged by genre, themes, game modes (such as co-op or single-player), and player perspectives (first-person, third-person).
- Visual Assets: Cover art, screenshots, and promotional artwork are hosted securely with dynamic sizing parameters.
- Credits and Companies: Detailed relational links connect individual titles to development studios and publishing houses.
Community moderation prevents duplicate entries and vandalism. Regular contributors earn trust levels that streamline the approval process for new game additions and correction flags.
The IGDB API: Access and Authentication
The IGDB API gives developers direct access to the entire game catalog without commercial cost barriers. Because Twitch owns the platform, authentication relies on the Twitch Developer Console.
Setting Up API Credentials
- Create or log into a Twitch Developer account.
- Navigate to the developer console and register a new application.
- Retrieve your unique Client ID and generate a corresponding Client Secret.
- Request an OAuth access token by sending a POST request to the Twitch token endpoint using the client credentials grant type.
curl -X POST "https://id.twitch.tv/oauth2/token?client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET&grant_type=client_credentials"
Once authenticated, every request to the REST base URL ([https://api.igdb.com/v4](https://api.igdb.com/v4)) requires both your Client-ID header and the generated Authorization: Bearer <token> header. Standard rate limits cap standard access at four requests per second, requiring efficient query construction.
Querying Data with Apicalypse
Instead of traditional SQL or rigid REST resource nesting, IGDB uses Apicalypse, a query language designed specifically for its API. Apicalypse lets you fetch precisely the fields you need in a single request, avoiding over-fetching.
For example, searching for a game title and returning its release date and cover art involves a simple POST request to the /games endpoint:
search "Cyberpunk";
fields name, release_dates.date, cover.url;
limit 5;
Advanced Filtering and Field Expansion
Field expansion allows you to pull relational data—such as developer names or platform titles—in the same payload rather than making separate calls.
- Multi-queries: Execute multiple distinct queries in a single HTTP request to batch operations efficiently.
- Sorting and Where Clauses: Filter results by rating, release year, or hype metrics using clean conditional operators.
- PopScore Integration: Access IGDB PopScore, which tracks popularity primitives like page visits and wishlist additions, updated every 24 hours.
Common Integration Pitfalls
Developers new to the platform often run into a few recurring bottlenecks. Avoiding these mistakes saves time and prevents rate-limiting blocks.
- Hardcoding Tokens: Access tokens expire. Implement an automated token caching and refresh routine rather than requesting a new token on every script execution.
- Ignoring Field Expansion: Making separate API requests for every platform or company ID quickly exhausts your four-requests-per-second limit. Always use nested fields.
- Neglecting Attribution: Commercial projects utilizing the API must display clear user-facing attribution linking back to IGDB.
Frequently Asked Questions
Is the IGDB API free for commercial projects?
Yes, the API is free for both non-commercial and commercial applications, provided you adhere to attribution guidelines and branding terms.
How often is game data updated?
Community submissions update the live database continuously. Commercial partners also have access to automated daily data dumps.
Can I store IGDB data on my own servers?
Yes, local caching and server-side data storage are permitted and encouraged to improve end-user application performance.
What is the maximum request rate allowed?
The standard public API enforces a limit of four requests per second per client ID.
