2ememain.be API2ememain.be ↗
Search listings, get listing details, seller profiles, and categories from 2ememain.be — Belgium's second-hand marketplace — via a structured JSON API.
curl -X GET 'https://api.parse.bot/scraper/38c7505b-327a-42b7-87b6-742ad0ed61ea/search_listings?limit=5&query=v%C3%A9lo&offset=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for listings on 2ememain.be with keywords, categories, and filters. Returns paginated results across the site's category tree.
| Param | Type | Description |
|---|---|---|
| limit | integer | Max results per page |
| query | string | Search keyword |
| offset | integer | Pagination offset |
| sort_by | string | Sort field (SORT_INDEX, OPTIMIZED, PRICE) |
| category | string | Category name or numeric category ID. Use get_categories to retrieve available category IDs. |
| distance | integer | Distance in km from postcode |
| postcode | string | Postal code for location-based search |
| condition | string | Item condition: new, as_new, or used |
| price_max | integer | Maximum price in euros |
| price_min | integer | Minimum price in euros |
| sort_order | string | Sort order: DECREASING or INCREASING |
{
"type": "object",
"fields": {
"facets": "array of facet objects for filtering (categories, price ranges, attributes)",
"listings": "array of listing objects with itemId, title, description, priceInfo, location, sellerInformation, categoryId, attributes, pictures",
"totalResultCount": "integer total number of matching listings"
},
"sample": {
"data": {
"facets": [
{
"key": "PriceCents",
"type": "AttributeRangeFacet"
}
],
"listings": [
{
"title": "Fender, Marshall, Blackstar, Line 6, Vox, Roland,...",
"itemId": "m2399028133",
"location": {
"cityName": "Asse",
"countryName": "Belgique"
},
"priceInfo": {
"priceType": "SEE_DESCRIPTION",
"priceCents": 0
},
"categoryId": 745,
"sellerInformation": {
"sellerId": 28710907,
"sellerName": "Thoma Okaze Asse"
}
}
],
"totalResultCount": 6269
},
"status": "success"
}
}About the 2ememain.be API
The 2ememain.be API gives access to Belgium's largest second-hand marketplace through 5 endpoints covering listing search, detailed item data, seller profiles, seller inventories, and category lookup. The search_listings endpoint accepts keyword queries, category IDs, postal codes, distance radii, condition filters, and sort options, returning paginated results with full price, location, and seller fields.
Search and Filter Listings
The search_listings endpoint is the primary entry point. Pass a query string alongside optional filters like condition (new, as_new, or used), postcode + distance for geo-bounded results, and category to restrict to a specific part of the 2ememain category tree. Results include an array of listing objects — each with itemId, title, description, priceInfo (priceCents and priceType), location, sellerInformation, categoryId, attributes, and pictures — plus a totalResultCount and a facets array you can use to understand available price ranges and attribute filters for a given query.
Listing Detail and Seller Data
get_listing_detail accepts an item_id (e.g. m2399028133) and returns enriched data for a single listing, including a product object containing schema.org Product structured data when the listing page exposes it. To investigate a seller further, take the sellerId from any listing's sellerInformation field and pass it to get_seller_profile, which returns review summaries (numberOfReviews, averageScore, reviewSystem), plus boolean flags for bankAccount, phoneNumber, and smbVerified. To see everything a seller currently has listed, get_seller_listings returns a paginated array of their active listings.
Category Lookup
get_categories returns a fixed map of category names to numeric IDs — including electric (745), acoustic (746), bass (747), amplifiers (748), and all_instruments (728). These IDs feed directly into the category parameter of search_listings. The endpoint currently covers the instruments section of the site; for other categories, the numeric ID can be discovered from listing categoryId fields returned in search results and passed directly to search_listings.
- Monitor price trends for second-hand items on 2ememain.be using
search_listingswith keyword and condition filters - Build a seller reputation checker by combining
get_seller_profilereview scores and verification flags - Aggregate a seller's entire active inventory using
get_seller_listingswith pagination - Create location-aware listing alerts by filtering
search_listingsonpostcodeanddistance - Extract structured product data from individual listings via the
productfield inget_listing_detail - Cross-reference
categoryIdvalues from search results to map the 2ememain category hierarchy
| 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 2ememain.be have an official developer API?+
What does `get_seller_profile` return beyond basic seller info?+
numberOfReviews, averageScore, and reviewSystem), plus three boolean flags: bankAccount (whether a bank account is linked), phoneNumber (whether a phone number is on file), and smbVerified (whether the seller holds SMB verified status). It does not return free-text reviews or individual review content.Does the API cover all categories on 2ememain.be, or only instruments?+
get_categories currently returns IDs for instruments subcategories (electric guitars, acoustic guitars, bass, amplifiers, and all instruments). All other categories are not pre-mapped by that endpoint. The API covers those categories via their numeric categoryId as found in listing responses. You can fork it on Parse and revise to add a broader category mapping endpoint.Can I retrieve sold or expired listings?+
search_listings and get_seller_listings reflect items currently available on the marketplace. Sold, closed, or archived listings are not covered. You can fork the API on Parse and revise it to add an endpoint targeting historical or completed listings if that data becomes accessible.How does pagination work across endpoints?+
search_listings and get_seller_listings both accept limit and offset integer parameters for pagination. The totalResultCount field in each response tells you how many total results exist, so you can calculate how many pages to walk. There is no cursor-based pagination — offset-based iteration is the supported pattern.