Discover/Packdraw API
live

Packdraw APIpackdraw.com

Access packs, battles, deals, live opens, and top opens leaderboard data from packdraw.com via 6 structured endpoints.

Endpoints
0
Updated
2mo ago

What is the Packdraw 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.

This API has no published endpoints yet. Check back soon.
Call it over HTTPgrab a free API key at signup
// select an endpoint above
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace packdraw-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""
PackDraw API Client
API for extracting packs, battles, and deals data from packdraw.com

Get your API key from: https://parse.bot/settings
"""

import os
import requests
from typing import Optional, Any, Dict


class ParseClient:
    """Client for interacting with the PackDraw API via Parse."""

    def __init__(self, api_key: Optional[str] = None):
        """
        Initialize the Parse API client.
        
        Args:
            api_key: Your Parse API key. If not provided, reads from PARSE_API_KEY env var.
        """
        self.base_url = "https://api.parse.bot"
        self.scraper_id = "c968b6cc-8f9b-4b96-82c2-0fbe563fc024"
        self.api_key = api_key or os.getenv("PARSE_API_KEY")
        
        if not self.api_key:
            raise ValueError("API key not provided and PARSE_API_KEY not set")

    def _call(self, endpoint: str, method: str = "POST", **params) -> Dict[str, Any]:
        """
        Make a request to the Parse API.
        
        Args:
            endpoint: The endpoint name to call
            method: HTTP method (GET or POST)
            **params: Parameters to pass to the endpoint
            
        Returns:
            Response data as dictionary
        """
        url = f"{self.base_url}/scraper/{self.scraper_id}/{endpoint}"
        headers = {
            "X-API-Key": self.api_key,
            "Content-Type": "application/json"
        }
        
        if method == "GET":
            response = requests.get(url, headers=headers, params=params)
        elif method == "POST":
            response = requests.post(url, headers=headers, json=params)
        else:
            raise ValueError(f"Unsupported HTTP method: {method}")
        
        response.raise_for_status()
        return response.json()

    def get_packs(self, **filters) -> Dict[str, Any]:
        """
        Fetch available packs with filtering, sorting, and pagination.
        
        Args:
            **filters: Optional filters like sort, limit, offset
            
        Returns:
            Dictionary containing packs data
        """
        return self._call("get_packs", method="GET", **filters)

    def get_battle_details(self, battle_id: str) -> Dict[str, Any]:
        """
        Fetch full details for a specific battle by ID.
        
        Args:
            battle_id: The ID of the battle to fetch
            
        Returns:
            Dictionary containing battle details
        """
        return self._call("get_battle_details", method="GET", id=battle_id)

    def list_deals_products(self, **filters) -> Dict[str, Any]:
        """
        List products in the deals section.
        
        Args:
            **filters: Optional filters and pagination params
            
        Returns:
            Dictionary containing deals products
        """
        return self._call("list_deals_products", method="GET", **filters)

    def get_homepage(self) -> Dict[str, Any]:
        """
        Fetch homepage content including featured packs and battles.
        
        Returns:
            Dictionary containing homepage data
        """
        return self._call("get_homepage", method="GET")

    def get_top_opens(self, **params) -> Dict[str, Any]:
        """
        Fetch the top recent opens leaderboard.
        
        Args:
            **params: Optional pagination and filter params
            
        Returns:
            Dictionary containing top opens data
        """
        return self._call("get_top_opens", method="GET", **params)

    def get_live_opens(self, **params) -> Dict[str, Any]:
        """
        Fetch the live opens feed.
        
        Args:
            **params: Optional pagination and filter params
            
        Returns:
            Dictionary containing live opens data
        """
        return self._call("get_live_opens", method="GET", **params)


def main():
    """Practical workflow example showing real PackDraw API usage."""
    
    # Initialize the client
    client = ParseClient()
    
    print("=" * 60)
    print("PackDraw API - Practical Usage Example")
    print("=" * 60)
    
    # Step 1: Get homepage to see featured content
    print("\n[Step 1] Fetching homepage featured packs and battles...")
    homepage = client.get_homepage()
    
    featured_packs = homepage.get("featured_packs", [])
    featured_battles = homepage.get("featured_battles", [])
    
    print(f"✓ Found {len(featured_packs)} featured packs")
    print(f"✓ Found {len(featured_battles)} featured battles")
    
    if featured_packs:
        print(f"\nTop Featured Pack: {featured_packs[0].get('name', 'N/A')}")
    
    # Step 2: Get all available packs with pagination
    print("\n[Step 2] Fetching available packs...")
    packs_data = client.get_packs(limit=10)
    
    packs = packs_data.get("packs", [])
    print(f"✓ Retrieved {len(packs)} packs")
    
    # Step 3: Get details for featured battles
    print("\n[Step 3] Fetching details for featured battles...")
    if featured_battles:
        for i, battle in enumerate(featured_battles[:3], 1):
            battle_id = battle.get("id")
            if battle_id:
                battle_details = client.get_battle_details(battle_id)
                battle_name = battle_details.get("name", "Unknown")
                battle_type = battle_details.get("type", "N/A")
                prize_pool = battle_details.get("prize_pool", "N/A")
                print(f"  {i}. {battle_name}")
                print(f"     Type: {battle_type} | Prize Pool: {prize_pool}")
    
    # Step 4: Check live opens activity
    print("\n[Step 4] Fetching live opens feed...")
    live_opens = client.get_live_opens(limit=5)
    
    opens_list = live_opens.get("opens", [])
    print(f"✓ Retrieved {len(opens_list)} recent opens")
    
    if opens_list:
        for i, open_item in enumerate(opens_list[:3], 1):
            user = open_item.get("user", "Anonymous")
            pack_name = open_item.get("pack_name", "Unknown Pack")
            pull_value = open_item.get("pull_value", "N/A")
            print(f"  {i}. {user} opened {pack_name} - Value: {pull_value}")
    
    # Step 5: Get top opens leaderboard
    print("\n[Step 5] Fetching top opens leaderboard...")
    top_opens = client.get_top_opens(limit=5)
    
    leaderboard = top_opens.get("leaderboard", [])
    print(f"✓ Top {len(leaderboard)} openers:")
    
    for i, entry in enumerate(leaderboard[:5], 1):
        username = entry.get("username", "Unknown")
        total_opens = entry.get("total_opens", 0)
        total_value = entry.get("total_value", 0)
        print(f"  {i}. {username} - {total_opens} opens (${total_value})")
    
    # Step 6: Check deals section
    print("\n[Step 6] Fetching deals products...")
    deals = client.list_deals_products(limit=5)
    
    deals_products = deals.get("products", [])
    print(f"✓ Found {len(deals_products)} deal products")
    
    if deals_products:
        for product in deals_products[:3]:
            product_name = product.get("name", "Unknown")
            discount = product.get("discount", "N/A")
            price = product.get("price", "N/A")
            print(f"  • {product_name} - {discount}% off (${price})")
    
    print("\n" + "=" * 60)
    print("✓ Example workflow completed successfully!")
    print("=" * 60)


if __name__ == "__main__":
    main()
All endpoints · 0 totalmissing one? ·

About the Packdraw API

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.

Reliability & maintenance

The Packdraw API is a managed, monitored endpoint for packdraw.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when packdraw.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official packdraw.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor Packdraw pack catalog changes and new pack releases using get_packs with pagination.
  • Track battle outcomes and participant data for specific events via get_battle_details.
  • Aggregate deals and discounted products from list_deals_products into 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_opens endpoint.
  • Analyze top-performing opens and user activity trends from the get_top_opens leaderboard.
  • Detect homepage promotion changes by polling get_homepage at regular intervals.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does Packdraw have an official public developer API?+
Packdraw does not publish an official public developer API or API documentation for third-party access. This Parse API provides structured access to the data available on the site.
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?+
No user account data, wallet balances, or private transaction history is exposed. The API covers public catalog data (packs, deals), battle records, homepage content, and the public leaderboard and live feed endpoints. You can fork this API on Parse and revise it to add any public-facing user profile pages if they become accessible.
How current is the live opens feed from `get_live_opens`?+
The 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?+
Not currently. The API provides the current top opens leaderboard via 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.
Page content last updated . Spec covers 0 endpoints from packdraw.com.
Related APIs in MarketplaceSee all →
rip.fun API
Browse and search trading cards, packs, and sets while tracking real-time market prices and price history on the rip.fun marketplace. Monitor trending cards, view detailed card and pack information, check recent mystery pack pulls, and analyze price changes to stay informed on the trading card market.
onepiece.gg API
Access One Piece Trading Card Game deck lists and card statistics to discover popular competitive strategies and build optimized decks. Search through detailed deck information to compare card choices and improve your gameplay.
royaleapi.com API
Track player profiles and battle histories, discover popular decks and card statistics, and explore clan information and leaderboards for Clash Royale. Access comprehensive game data and competitive rankings to improve your gameplay strategy and tournament participation.
en.onepiece-cardgame.com API
Search and explore One Piece trading card data across all series, view detailed card information including stats, abilities, and artwork, and stay up to date with the latest news, events, and product releases from the official game site. Browse recommended deck strategies and discover upcoming tournaments and expansions.
cardmarket.com API
Search and browse trading cards across Europe's largest marketplace, accessing detailed card information, listings, seller profiles, and finding the best bargains all in one place. Explore games and expansions to discover available singles and compare prices from multiple sellers.
snkrdunk.com API
Access data from snkrdunk.com.
miniaturemarket.com API
Search for miniature and tabletop gaming products, browse items by category, and access detailed product information including customer reviews and current deals from Miniature Market. Find exactly what you need with comprehensive product listings and real-time pricing data to make informed purchasing decisions.
ygoprodeck.com API
Search and retrieve detailed Yu-Gi-Oh! card information including attributes, effects, and images from the comprehensive YGOProDeck database. Browse the complete card catalog or look up specific cards to find everything you need about their stats and abilities.