Discover/eFarmz API
live

eFarmz APIefarmz.be

Access eFarmz.be weekly meal boxes, product search, fruits & vegetables listings, and full product details via a structured JSON API.

Endpoint health
verified 6d ago
search_products
get_weekly_mealboxes
get_product_detail
list_fruits_and_vegetables
4/4 passing latest checkself-healing
Endpoints
4
Updated
13d ago

What is the eFarmz API?

The eFarmz.be API exposes 4 endpoints covering Belgium's organic meal box service: retrieve weekly cooking boxes by ISO week number via get_weekly_mealboxes, search the product catalog by keyword, fetch detailed product records including allergens and brand data, and list every item in the fruits and vegetables category across all sub-categories. Responses include fields like primary_tag, price, origin, brand, and category hierarchy.

This call costs3 credits / call— charged only on success
Try it
ISO week number (1-53). For example: '23' corresponds to 01/06-07/06 in 2026, '24' to 08/06-14/06, etc.
4-digit year for the period lookup.
Language for meal box names.
api.parse.bot/scraper/915f9bce-6e61-4654-9f7f-7e32bc0e82a9/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/915f9bce-6e61-4654-9f7f-7e32bc0e82a9/get_weekly_mealboxes?week=38&year=2026&language=fr' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 4 totalmissing one? ·

Get the first 18 cooking meal box names and their tags available for a given week. Each meal box has one or more tags from: Classique, Famille, Express, Healthy, Veggie. A primary_tag is determined by priority order (Healthy > Express > Veggie > Famille > Classique). Returns cooking boxes only (excludes reheat boxes), in the chosen language (French or Dutch).

Input
ParamTypeDescription
weekrequiredstringISO week number (1-53). For example: '23' corresponds to 01/06-07/06 in 2026, '24' to 08/06-14/06, etc.
yearstring4-digit year for the period lookup.
languagestringLanguage for meal box names.
Response
{
  "type": "object",
  "fields": {
    "week": "integer - ISO week number",
    "year": "integer - year",
    "total": "integer - number of meal boxes returned (max 18)",
    "period": "string - the YYYYWW period code sent to the site",
    "language": "string - language code used ('fr' or 'nl')",
    "mealboxes": "array of meal box objects, each containing position (integer, 1-based order on the website), name (string), primary_tag (string, highest priority tag), and tags (array of strings, all applicable tags sorted by priority)"
  },
  "sample": {
    "data": {
      "week": 24,
      "year": 2026,
      "total": 18,
      "period": "202624",
      "language": "fr",
      "mealboxes": [
        {
          "name": "Tagliata de boeuf, sauce au persil et aubergines grillées au citron",
          "tags": [
            "Classique"
          ],
          "position": 1,
          "primary_tag": "Classique"
        },
        {
          "name": "Riz au chorizo et poivrons",
          "tags": [
            "Express"
          ],
          "position": 2,
          "primary_tag": "Express"
        }
      ]
    },
    "status": "success"
  }
}

About the eFarmz API

Weekly Meal Boxes

The get_weekly_mealboxes endpoint takes an ISO week number (1–53) and an optional year to return up to 18 cooking box options available that week on eFarmz.be. Each meal box object includes its position on the site, name, and a primary_tag derived from a fixed priority order: Healthy > Express > Veggie > Famille > Classique. A period field returns the YYYYWW code used for the lookup, and the language parameter switches names between French (fr) and Dutch (nl).

Product Search and Detail

search_products accepts a query string (e.g. 'tomate', 'fromage') and returns up to 10 matching products. Each result includes id, name, slug, price in EUR, brand, origin (country code), conditioning, tags, categories, and is_available status. The product_id values from search results feed directly into get_product_detail, which returns extended data: full description, ingredients, allergen information, a brand object with name, description and image, deposit amount, and the full category hierarchy.

Fruits and Vegetables Listing

list_fruits_and_vegetables walks the entire eFarmz fruits and vegetables shop category — covering vegetables, fruits, organic baskets, and herbs — and returns every product found. The response includes total, total_pages, and pages_fetched so you can verify complete traversal. Each product entry carries an id, name, slug, url in the requested language, and summary pricing and category fields consistent with the search endpoint.

Reliability & maintenanceVerified

The eFarmz API is a managed, monitored endpoint for efarmz.be — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when efarmz.be 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 efarmz.be 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.

Last verified
6d ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
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
  • Build a weekly meal plan tracker that pulls current box options and filters by primary_tag (e.g. only Veggie or Healthy boxes).
  • Aggregate eFarmz product prices for organic produce price monitoring across Belgian e-commerce.
  • Generate a structured catalog of all eFarmz fruits and vegetables using list_fruits_and_vegetables for a comparison shopping tool.
  • Look up allergen and ingredient details for specific products via get_product_detail to support dietary filtering applications.
  • Map product origin country codes from search_products results to visualise sourcing geography for organic goods.
  • Feed meal box names and tags into a recommendation engine that matches boxes to user dietary preferences.
  • Track week-over-week changes in meal box availability by polling get_weekly_mealboxes across consecutive ISO week numbers.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does eFarmz.be have an official public developer API?+
eFarmz.be does not publish an official public developer API or documented API program. This Parse API is the structured access point for that data.
How does get_weekly_mealboxes determine the primary_tag for each box?+
Each meal box can carry multiple tags (Classique, Famille, Express, Healthy, Veggie). The endpoint applies a fixed priority order — Healthy > Express > Veggie > Famille > Classique — and assigns the highest-priority matching tag as primary_tag. The full tag list for each box is also returned so you can apply your own logic.
Does the API return meal box recipe details or ingredient lists?+
Not currently. get_weekly_mealboxes returns box names, tags, position, and the period code, but not recipe steps or per-box ingredient lists. get_product_detail does return ingredients and allergens for individual shop products. You can fork this API on Parse and revise it to add a recipe detail endpoint if that data is accessible on the site.
How many products does list_fruits_and_vegetables return, and is it paginated?+
The endpoint returns all unique products in the eFarmz fruits and vegetables category across all sub-categories at the time of the call. The response includes total_pages (pages the site reports) and pages_fetched (pages actually read) so you can confirm full coverage. Roughly 32 products appear per page on the source listing.
Does the API cover eFarmz product categories beyond fruits and vegetables?+
The dedicated listing endpoint covers only the Fruits et Légumes category. Other shop categories — such as dairy, pantry, or charcuterie — are not covered by a dedicated listing endpoint. search_products can surface items from those categories by keyword. You can fork this API on Parse and revise it to add listing endpoints for additional categories.
Page content last updated . Spec covers 4 endpoints from efarmz.be.
Related APIs in Food DiningSee all →