rip APIrip.fun ↗
Access rip.fun card details, pack pricing, price history, trending market data, and set listings via 12 structured API endpoints.
What is the rip API?
The rip.fun API gives developers structured access to the rip.fun digital Pokémon card marketplace across 12 endpoints, covering card details, pack data, price history, and on-chain trading activity. get_card_price_change returns 24-hour and 7-day price deltas alongside a human-readable analysis and a good-buy confidence score, while get_card_activity exposes individual sales, listings, offers, and transfers tied to specific card IDs.
curl -X GET 'https://api.parse.bot/scraper/e38c7481-b114-4e6c-9f4f-36374c3ad559/search?limit=5&query=charizard' \ -H 'X-API-Key: $PARSE_API_KEY'
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 rip-fun-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.
"""Walkthrough: rip.fun SDK — search cards, inspect pricing, browse sets."""
from parse_apis.rip_fun_api import RipFun, PriceRange, NotFound
client = RipFun()
# Search for cards across the platform
results = client.cards.search(query="charizard", limit=5)
print(f"Found {len(results.cards)} cards matching 'charizard'")
for card in results.cards[:3]:
print(f" {card.name} ({card.id}) — ${card.raw_price}")
# Navigate from search results to expansion sets
if results.sets:
found_set = results.sets[0]
print(f"\nSet from search: {found_set.name} (id={found_set.id})")
# Construct a card by ID and check its price movement
card = client.card(id="sv8pt5-1")
change = card.price_change()
print(f"\nCard price change: 24h={change.twenty_four_hour_change}%, 7d={change.seven_day_change}%")
print(f" Reason: {change.reason}, Good buy: {change.good_buy_percentage}%")
# Fetch 7-day price history using the PriceRange enum
for point in card.price_history(range=PriceRange.SEVEN_DAYS, limit=3):
print(f" {point.timestamp}: ${point.price} (source: {point.source})")
# Browse cards in an expansion set — paginated automatically
prismatic = client.expansionset(id="sv8pt5")
for set_card in prismatic.cards(limit=3):
print(f" {set_card.name} [{set_card.rarity}] — ${set_card.raw_price}")
# Typed error handling: catch NotFound for a bad card ID
try:
bad_card = client.card(id="nonexistent-999")
bad_card.price_change()
except NotFound as exc:
print(f"\nExpected error: {exc}")
print("\nExercised: cards.search / card.price_change / card.price_history / expansionset.cards / NotFound")
Full-text search across cards, packs, sets, and user profiles on rip.fun. Returns matching results in each category up to the specified limit. Query matches card names, set names, and usernames.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of results to return per category. |
| queryrequired | string | Search keyword (e.g. 'charizard', 'pikachu'). |
{
"type": "object",
"fields": {
"sets": "array of matching expansion set objects",
"cards": "array of matching card objects with id, name, raw_price, image URLs",
"users": "array of matching user profile objects",
"products": "array of matching product/pack objects"
},
"sample": {
"data": {
"sets": [],
"cards": [
{
"id": "sv8pt5-1",
"name": "Eevee",
"raw_price": "0.50"
}
],
"users": [],
"products": []
},
"status": "success"
}
}About the rip API
Card Data and Pricing
The get_card_detail endpoint accepts a card_id in setid-number format (e.g. sv8pt5-1, ecard1-6vh) and returns full card attributes, pricing, and image URLs. get_card_price_history adds time-series context via a range parameter accepting 7d, 30d, 1yr, or all, returning an array of timestamped price points. For quick directional signals, get_card_price_change delivers twenty_four_hour_change, seven_day_change, and good_buy_percentage in a single lightweight call.
Pack and Set Browsing
get_pack_detail and get_pack_price_history mirror the card endpoints for booster packs, with pack price history sourcing TCGPlayer aggregated retail and market prices. get_explore_sets returns all expansion sets on the platform. get_set_cards lists every card within a set — identified by set_id — and supports page and limit parameters; each card object includes id, name, raw_price, rarity, and image URLs alongside a clip_embedding field.
Marketplace Activity and Trending
get_market_trending_cards retrieves the current trending card listings from the marketplace homepage. On-chain activity — sales, transfers, and physical openings — is available per-card via get_card_activity and per-pack via get_pack_activity. The pack activity response includes a userMap object keying user addresses to profile data, a boolean success flag, and a _truncated field that appears when a very active pack's history had to be partially recovered. get_mystery_pack_recent_pulls returns the global recent-pulls feed, including pack name, image URL, price, tierId, and createdAt timestamp for each pull.
Search
The search endpoint accepts a query string and optional limit, and returns matched results across four categories simultaneously: sets, cards, packs, and users. Card results include id, name, raw_price, and image URLs, making it straightforward to resolve card IDs for downstream detail or price history calls.
The rip API is a managed, monitored endpoint for rip.fun — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when rip.fun 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 rip.fun 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?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track daily price swings on specific Pokémon cards using
twenty_four_hour_changeandseven_day_changefromget_card_price_change. - Build a portfolio tracker that monitors
raw_priceacross a set's full card list viaget_set_cardswith pagination. - Alert users when trending cards appear on the marketplace homepage by polling
get_market_trending_cards. - Aggregate recent mystery pack pull results for community analytics using
get_mystery_pack_recent_pulls. - Audit on-chain transfer and sales history for a specific booster pack using the
activityarray fromget_pack_activity. - Compare pack price trends against card single prices by pairing
get_pack_price_historyandget_card_price_historyon the same set. - Resolve card and pack IDs from user-entered keywords using the
searchendpoint before fetching detailed pricing data.
| 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 | 100 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 rip.fun have an official developer API?+
What does `get_card_activity` return for a card with no trading history?+
get_card_activity returns an empty activities array for cards that have not been traded, listed, or transferred on the platform. When activity exists, each object includes a type (sale, listing, offer, transfer), price, timestamp, and the relevant user addresses.How does pagination work for `get_set_cards`, and is there a hard limit?+
get_set_cards accepts integer page and limit query parameters. The response always includes a total field showing the full count of cards in the set, so callers can compute how many pages to request. No documented hard cap on limit is specified in the endpoint definition, so testing at realistic page sizes is advisable.Does the API expose individual user portfolio holdings or collection data?+
search and user address mappings in get_pack_activity, but does not include endpoints for querying a specific user's owned cards or collection inventory. You can fork this API on Parse and revise it to add a user-collection endpoint.Can I get sub-24-hour price history granularity from `get_card_price_history`?+
range parameter accepts 7d, 30d, 1yr, and all — there is no intraday or hourly resolution option. For near-real-time directional signals, get_card_price_change provides the 24-hour percentage change. If finer-grained intervals are needed, you can fork this API on Parse and revise it to target a more granular price history resource.