API explorer
Build a request. Run it. See what comes back.
Every endpoint below comes from the same operation schemas that power the REST API and MCP tools. Choose an endpoint to see its parameters, generate a code example and send a real request.
Bring your API key
Create a personal key in Settings → Account → Developer access. In an endpoint's playground, enter the full key as the bearer token. Requests go directly to this site's API. Authentication is kept in your browser tab's session, so close the tab when you're finished on a shared device.
Explore by resource
Card catalog
Search cards, browse sets and series, and look up Pokémon and illustrators.
Your collection
Manage binders, owned and wanted cards, sharing, artwork and show purchases.
Prices & insights
Read price evidence, compare listings, check deals and follow price history.
Account & preferences
Read settings, update your identity and manage partner connections.
Before you send a request
- Real requests, real changes. Write operations change your account. Start with a read-only key and a GET request.
- Permissions apply. The explorer uses the same subscription, permissions and rate limits as your own integrations.
- Retry safely. Creating a binder requires an
Idempotency-Key. Settings changes use the fingerprint from your last read, and collection storage commands use current revisions with a retry-stableoperationId.
See API conventions for pagination, errors and limits. Prefer an AI assistant? Connect through MCP instead.
Codex
Give your coding agent access to Holo Folder.
Search cards GET
Browse all card printings, including Trainers and Energy, with pagination. Records declare game:pokemon; IDs are globally unique opaque application IDs, not provider-local keys. Required permissions: `catalog:read`. MCP tool: `list_cards`.