Argiro APIargiro.gr ↗
Search and retrieve Greek recipes from argiro.gr. Get structured recipe data including ingredients, instructions, timing, servings, and category via 3 endpoints.
What is the Argiro API?
The Argiro.gr API provides access to Greek recipes from Argiro Barbarigou's cooking website via 3 endpoints. The get_recipe endpoint returns fully structured recipe data — ingredients, step-by-step instructions, cook time in ISO 8601 format, servings, cuisine, and keywords — keyed by URL slug. Pair it with search_recipes or get_latest_recipes_by_category to discover recipes across the site's full category hierarchy.
curl -X GET 'https://api.parse.bot/scraper/273ef8c2-d9a5-40c5-87c0-79e8fa823c57/search_recipes?query=%CE%BA%CE%BF%CF%84%CF%8C%CF%80%CE%BF%CF%85%CE%BB%CE%BF' \ -H 'X-API-Key: $PARSE_API_KEY'
Search recipes on argiro.gr by keyword. Returns paginated recipe summaries (12 per page) with title, slug, category, and image. The site is Greek, so Greek search terms (e.g. 'κοτόπουλο') produce more results than English equivalents. An empty result set is valid for queries with no matches.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (starts at 1). |
| queryrequired | string | Search query for recipes. Greek terms recommended (e.g. 'κοτόπουλο' for chicken, 'σοκολάτα' for chocolate). |
{
"type": "object",
"fields": {
"page": "Current page number",
"query": "The search query that was used",
"recipes": "Array of recipe summaries with title, slug, url, category, and image",
"has_next": "Whether there is a next page",
"total_pages": "Total number of pages available",
"total_results": "Total number of matching recipes"
},
"sample": {
"data": {
"page": 1,
"query": "κοτόπουλο",
"recipes": [
{
"url": "https://www.argiro.gr/recipe/fileto-stithos-kotopoulo-me-pesto-vasilikou/",
"slug": "fileto-stithos-kotopoulo-me-pesto-vasilikou",
"image": "https://www.argiro.gr/wp-content/uploads/2026/07/fileto-stithos-kotopoulo-pesto-360x270.jpg",
"title": "Φιλέτο στήθος κοτόπουλο με πέστο βασιλικού",
"category": "ΚΟΤΟΠΟΥΛΟ"
}
],
"has_next": true,
"total_pages": 11,
"total_results": 127
},
"status": "success"
}
}About the Argiro API
Searching and Browsing Recipes
The search_recipes endpoint accepts a query string and an optional page integer. It returns up to 12 recipe summaries per page, each containing title, slug, url, category, and image. The response includes total_results, total_pages, and a has_next boolean for straightforward pagination. Because the site is in Greek, queries using Greek terms — for example κοτόπουλο for chicken or σοκολάτα for chocolate — consistently return more results than transliterated or English equivalents.
Fetching Full Recipe Details
Pass a slug obtained from search_recipes or get_latest_recipes_by_category to get_recipe to retrieve the full recipe record. The response includes name, description, author, cuisine, category, keywords, servings, cook_time (ISO 8601 duration, e.g. PT45M), image, and url. This is the only endpoint that exposes ingredient lists and step-by-step instructions.
Browsing by Category
The get_latest_recipes_by_category endpoint takes a category slug that mirrors the site's URL structure. Top-level slugs like glika (sweets) or almira (savory) return that section's newest recipes. Subcategories follow a path format: almira/kotopoulo for chicken dishes, almira/salates for salads. Each page returns up to 12 summaries with the same fields as search_recipes. Use this endpoint when you need the latest content in a specific section rather than keyword-driven results.
The Argiro API is a managed, monitored endpoint for argiro.gr — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when argiro.gr 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 argiro.gr 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 Greek recipe discovery app indexed by category using
get_latest_recipes_by_categorywith subcategory slugs - Populate a meal-planning tool with cook times and serving sizes from
get_recipe - Create a recipe search interface that autocompletes Greek ingredient names and queries
search_recipes - Aggregate weekly new recipe releases across multiple categories for a newsletter digest
- Extract structured ingredient lists and instructions for nutritional analysis pipelines
- Build a keyword-based recipe recommendation engine using the
keywordsandcategoryfields returned byget_recipe
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 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.
Does argiro.gr have an official developer API?+
What does `get_recipe` return beyond the summary fields from search?+
get_recipe is the only endpoint that returns full recipe content: a text description, the ingredient list, step-by-step instructions, cook_time in ISO 8601 duration format, servings, cuisine, and comma-separated keywords. The search and category endpoints return only title, slug, url, category, and image.Does the search endpoint support filtering by category or cook time?+
search_recipes endpoint filters only by the query string and page number. Filtering by category, cook time, or servings is not currently supported there. get_latest_recipes_by_category narrows results by category slug, but finer filters are not exposed. You can fork this API on Parse and revise it to add filtering parameters to the missing endpoint.Are nutrition facts available for recipes?+
How does pagination work across the three endpoints?+
page parameter (integer, starts at 1) controls which page is returned. The response always includes total_pages, total_results (search only), and has_next so you can determine whether to fetch additional pages.