Fandom APIblox-fruits.fandom.com ↗
Access Blox Fruits wiki data via API: fruit names, rarity tiers, types, money/Robux prices, image URLs, and full movesets with hotkey descriptions.
What is the Fandom API?
This API exposes data from the Blox Fruits Fandom wiki across 2 endpoints, covering every fruit's name, rarity, type, in-game money and Robux prices, image URL, and detailed moveset. The get_fruits endpoint returns the full fruit catalog with optional rarity filtering, while get_fruit_details retrieves a single fruit's complete move list — including hotkey, move name, and description — along with all pricing and classification fields.
curl -X GET 'https://api.parse.bot/scraper/78cf8155-3819-45d0-b799-92f840a94827/get_fruits?rarity=Common' \ -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 blox-fruits-fandom-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.
"""Walkthrough: Blox Fruits Wiki SDK — list fruits, filter by rarity, get details."""
from parse_apis.blox_fruits_fandom_com_api import BloxFruits, Rarity, FruitType, FruitNotFound
client = BloxFruits()
# List all Mythical fruits — limit caps total items fetched
for fruit in client.fruit_summaries.list(rarity=Rarity.MYTHICAL, limit=5):
print(fruit.name, fruit.rarity, fruit.type, fruit.money_price)
# Drill into one fruit's full details (moves, m1 info)
summary = client.fruit_summaries.list(rarity=Rarity.LEGENDARY, limit=1).first()
if summary:
detail = summary.details()
print(detail.name, detail.type, detail.m1_enabled)
for move in detail.moves[:3]:
print(f" [{move.key}] {move.name}: {move.description[:60]}")
# Typed error handling: catch a fruit that doesn't exist
try:
first_fruit = client.fruit_summaries.list(limit=1).first()
if first_fruit:
full = first_fruit.details()
print(full.name, full.image_url)
except FruitNotFound as exc:
print(f"Fruit not found: {exc.fruit_name}")
print("exercised: fruit_summaries.list / details / FruitNotFound")
Retrieves all available Blox Fruits with their name, rarity, type, in-game prices, and image URL. Results can be filtered by rarity. Returns fruits in their natural game ordering.
| Param | Type | Description |
|---|---|---|
| rarity | string | Filter fruits by rarity tier. Case-insensitive. When omitted, all fruits are returned. |
{
"type": "object",
"fields": {
"total": "integer",
"fruits": "array of fruit summary objects with name, rarity, type, money_price, robux_price, image_url, wiki_url"
},
"sample": {
"data": {
"total": 41,
"fruits": [
{
"name": "Rocket",
"type": "Natural",
"rarity": "Common",
"wiki_url": "https://blox-fruits.fandom.com/wiki/Rocket",
"image_url": "https://static.wikia.nocookie.net/roblox-blox-piece/images/c/cb/Rocket_Fruit.png/revision/latest?cb=20231027120039",
"money_price": 5000,
"robux_price": 50
}
]
},
"status": "success"
}
}About the Fandom API
Fruit Catalog Endpoint
The get_fruits endpoint returns the full list of Blox Fruits in their natural game ordering. Each entry in the fruits array includes name, rarity, type, money_price, robux_price, image_url, and wiki_url. The optional rarity parameter filters results to a single tier (e.g. Legendary, Mythical, Common) and is case-insensitive. The response also includes a total count of matched fruits.
Per-Fruit Detail Endpoint
The get_fruit_details endpoint accepts a single required parameter, fruit_name, which must match the wiki page title exactly — including hyphens and capitalization (e.g. T-Rex, Kitsune, Dragon). The response returns the fruit's type, rarity, money_price, robux_price, image_url, wiki_url, and an m1_enabled field indicating basic attack availability. The moves array lists every ability with its key (hotkey), name, and description, giving a full picture of the fruit's combat kit.
Data Coverage and Quirks
Prices are returned as integers or null — a null money_price typically indicates the fruit is not purchasable with in-game Beli, and a null robux_price means it has no Robux purchase option. Fruit names are case-sensitive inputs; submitting dragon instead of Dragon will not resolve correctly. The wiki reflects community-maintained data, so field completeness varies slightly between fruits depending on how thoroughly each wiki page has been edited.
The Fandom API is a managed, monitored endpoint for blox-fruits.fandom.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when blox-fruits.fandom.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 blox-fruits.fandom.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?+
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?+
- Build a fruit comparison tool that filters by rarity tier using the
rarityparam and displaysmoney_priceandrobux_priceside by side. - Generate a Discord bot command that looks up any fruit's full moveset via
get_fruit_detailsand returns hotkeys and descriptions. - Create a budget guide showing which fruits are available for in-game Beli by filtering for non-null
money_pricevalues. - Populate a game wiki mirror or fan site with up-to-date fruit images using the
image_urlfield fromget_fruits. - Build a tier-list UI that groups all fruits by
rarityandtypeusing the catalog endpoint's structured output. - Develop a move-reference sheet for a specific fruit by fetching its
movesarray with key bindings and ability descriptions.
| 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 Blox Fruits Fandom have an official developer API?+
What does the `rarity` filter in `get_fruits` accept, and does it affect result ordering?+
rarity parameter accepts any rarity tier string (e.g. Common, Uncommon, Rare, Legendary, Mythical) and is case-insensitive. Filtered results retain the natural in-game ordering; only the matched tier is returned. The total field in the response reflects the filtered count.Does the API cover fruit trading prices or current market values?+
money_price and robux_price from the wiki — player-to-player trading values and demand tiers are not included. You can fork this API on Parse and revise it to add an endpoint pulling from community trading resources.What happens if a fruit has no in-game Beli price?+
money_price is returned as null for fruits that cannot be purchased with Beli. Similarly, robux_price is null when no Robux purchase exists. Both fields are integers when a price is available.Does the API include fruit awakening details or stat values like damage multipliers?+
moves array, along with rarity, type, and pricing. Awakening-specific moves and numeric stat values are not included as separate fields. You can fork this API on Parse and revise it to add an endpoint targeting awakening move data.