packdraw.com APIpackdraw.com ↗
Access packs, battles, deals, live opens, and top opens leaderboard data from packdraw.com via 6 structured endpoints.
// select an endpoint above
About the packdraw.com API
The Packdraw API exposes 6 endpoints covering packs, battles, deals, and live activity on packdraw.com. The get_packs endpoint returns available packs with filtering and pagination support, while get_battle_details delivers full metadata for a specific battle by ID. Additional endpoints surface homepage featured content, the deals product catalog, a top opens leaderboard, and a real-time live opens feed.
Packs and Battles
The get_packs endpoint retrieves the full catalog of available packs on Packdraw, supporting filtering, sorting, and pagination so you can segment by pack type or price range. For battle-specific data, get_battle_details accepts a battle ID and returns the complete detail record for that battle, including participant and outcome information associated with that event.
Deals and Homepage Content
list_deals_products returns the product listings currently featured in the Packdraw deals section, useful for tracking discounted or promoted items. The get_homepage endpoint fetches the site's homepage content, including featured packs and active battles surfaced at the top of the page — giving a snapshot of what Packdraw is currently promoting.
Live Activity and Leaderboards
Two endpoints capture real-time user activity: get_live_opens returns the live opens feed showing recent pack openings as they occur, while get_top_opens fetches the top opens leaderboard, ranking users or items by recent open volume. These endpoints are particularly useful for monitoring activity trends or building dashboards that reflect current site engagement.
- Monitor Packdraw pack catalog changes and new pack releases using
get_packswith pagination. - Track battle outcomes and participant data for specific events via
get_battle_details. - Aggregate deals and discounted products from
list_deals_productsinto a price comparison tool. - Build a dashboard showing featured packs and active battles pulled from
get_homepage. - Display a real-time feed of pack openings by consuming the
get_live_opensendpoint. - Analyze top-performing opens and user activity trends from the
get_top_opensleaderboard. - Detect homepage promotion changes by polling
get_homepageat regular intervals.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Packdraw have an official public developer API?+
What does `get_battle_details` return versus `get_packs`?+
get_packs returns a paginated, filterable list of available packs across the catalog. get_battle_details is scoped to a single battle identified by ID and returns full details specific to that battle event, including participant and result data, rather than pack-level information.Does the API expose individual user account history or wallet balances?+
How current is the live opens feed from `get_live_opens`?+
get_live_opens endpoint reflects the live opens feed as it appears on the Packdraw site at the time of the request. Freshness is tied to when you call the endpoint — there is no push or webhook mechanism, so polling frequency determines how up-to-date your data is.Does the API cover historical pack opening statistics or past leaderboard snapshots?+
get_top_opens and the current live feed via get_live_opens, but does not return historical time-series data or archived leaderboard states. You can fork this API on Parse and revise it to store and expose historical snapshots if that endpoint pattern becomes available.