FunPay APIfunpay.com ↗
Access FunPay.com game categories, marketplace listings, pricing, and seller profiles via 5 structured API endpoints. Search games, browse offers, and track sellers.
What is the FunPay API?
The FunPay API exposes 5 endpoints covering the FunPay gaming marketplace — from searching games and browsing category listings to pulling full seller profiles. The get_lots_by_category endpoint returns live offer data including price, seller rating, review count, and stock status for any supported lot category. Whether you're tracking in-game currency prices or researching seller reputation, the API gives you structured access to public marketplace data.
curl -X GET 'https://api.parse.bot/scraper/b07b6749-5fbe-4b92-ac50-82aab4087ce5/get_game_categories?query=Lost+Ark' \ -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 funpay-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.
from parse_apis.funpay_marketplace_api import FunPay, GameType, Category
funpay = FunPay()
# Search for games matching "Lost Ark"
for game in funpay.games.search(query="Lost Ark"):
print(game.name, game.lot_id, game.type)
# Get the game page with all categories
page = funpay.gamepages.get(game_id="91")
print(page.title, page.game_id)
for cat in page.categories:
print(cat.name, cat.count, cat.lot_id)
# Construct a category and browse its listings
accounts = funpay.category(lot_id="332")
for listing in accounts.listings():
print(listing.description, listing.price_raw, listing.seller.name)
# Fetch a seller profile
seller = funpay.sellerprofiles.get(user_id="8083104")
print(seller.name, seller.rating, seller.registration_date)
for item in seller.listings:
print(item.section, item.price)
# Get the full game catalog
catalog = funpay.gamecatalogs.fetch()
for group_name, entries in catalog.groups.items():
for entry in entries[:3]:
print(entry.name, entry.url)
Search for games available on FunPay and retrieve their categories. Returns matching games with sub-categories (e.g. Gold, Accounts, Items). A non-empty query is required to get results; an empty query returns an empty games array.
| Param | Type | Description |
|---|---|---|
| query | string | Search query to filter games. At least 1 character is required to return results. |
{
"type": "object",
"fields": {
"games": "array of game objects with name, url, lot_id, and type (chips or lots)"
},
"sample": {
"data": {
"games": [
{
"url": "https://funpay.com/en/chips/91/",
"name": "Lost Ark",
"type": "chips",
"lot_id": "91"
},
{
"url": "https://funpay.com/en/lots/332/",
"name": "Accounts",
"type": "lots",
"lot_id": "332"
}
]
},
"status": "success"
}
}About the FunPay API
Game Discovery
Two endpoints handle game discovery. get_game_list_by_letter returns the full FunPay game directory grouped by alphabetical header — no parameters required. Each entry includes a name and url. For targeted lookup, get_game_categories accepts a query string (minimum one character) and returns matching games along with their sub-categories such as Gold, Accounts, or Items. Each result carries a lot_id and a type field (chips or lots) that determines which downstream endpoints will accept it.
Category and Listing Data
get_game_page takes a numeric game_id (e.g. 91 for Lost Ark) and returns all sub-categories for that game — each with a name, lot_id, listing count, and url. This is the standard way to discover valid lot IDs before fetching listings. get_lots_by_category then accepts one of those lot_id values and returns all active offers. Each listing object includes offer_id, description, price_raw, stock, and a nested seller object with name, rating, and reviews. An optional query parameter filters listings by description text. Note that only lots-type category IDs are accepted; passing a chips-type ID returns an upstream error.
Seller Profiles
get_seller_profile requires a numeric user_id (usernames are not accepted). It returns the seller's name, rating, reviews_count, registration_date, and a listings array showing their current offers with section, description, and price. New or inactive accounts may return empty rating and listing fields.
The FunPay API is a managed, monitored endpoint for funpay.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when funpay.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 funpay.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?+
- Monitor price trends for in-game items or currency across FunPay categories using
price_rawfromget_lots_by_category - Build a seller reputation checker by pulling
rating,reviews_count, andregistration_datefromget_seller_profile - Index the full FunPay game catalog using
get_game_list_by_letterfor search or directory features - Alert on new listings in a specific game category by polling
get_lots_by_categorywith a keywordqueryfilter - Compare active offer counts across sub-categories for a game using the
countfield fromget_game_page - Audit a seller's current inventory by combining profile data and the
listingsarray fromget_seller_profile - Map game IDs to their available category lot IDs for automated category traversal pipelines
| 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 FunPay have an official public developer API?+
What is the difference between 'chips' and 'lots' category types, and does it matter for fetching listings?+
type field returned by get_game_categories will be either chips (currency-style categories) or lots (item or account categories). get_lots_by_category only accepts lots-type IDs. Passing a chips-type lot ID to that endpoint returns an upstream error, so you should check the type field before calling it.Can I look up a seller by username instead of a numeric ID?+
get_seller_profile requires a numeric user_id. Usernames are not accepted. You can obtain a numeric user ID from seller objects in get_lots_by_category results or from a FunPay profile URL directly.Does the API return buyer-side data such as purchase history or order status?+
Are listings paginated, and is there a way to retrieve older or off-page offers?+
get_lots_by_category returns the listings shown on the public category page without pagination controls. Offers not visible on that page are not currently returned. You can fork the API on Parse and revise it to add pagination or deeper listing retrieval if the source supports it.