Lamomeplage APIlamomeplage.com ↗
Access page content, menu details, and site structure for La Môme Plage, a Mediterranean beach restaurant in Cannes, via 2 REST endpoints.
What is the Lamomeplage API?
The La Môme Plage API provides structured access to content from the Cannes Mediterranean beach restaurant's website through 2 endpoints. Use list_pages to retrieve the full site navigation with slugs, titles, and modification dates, or call get_page_content by page ID or slug to extract text content, images, and links from any published page — including the menu (nos-cartes), private dining, and restaurant history pages.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/6f03b333-85d7-4455-acaa-7a732313af57/list_pages' \ -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 lamomeplage-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.
"""La Môme Plage: browse site pages and extract restaurant content."""
from parse_apis.la_môme_plage_api import LaMomePlage, Slug, PageNotFound
client = LaMomePlage()
# List all published pages on the site
for page in client.pages.list(limit=5):
print(page.title, page.slug, page.modified)
# Fetch full page content by slug using the Slug enum
menu_page = client.pages.list(limit=1).first()
if menu_page:
detail = menu_page.details()
print(detail.title, detail.text_content[:100])
for link in detail.links:
print(link.text, link.url)
# Handle a missing page gracefully
try:
missing = client.pages.get(page_id="99999")
print(missing.title)
except PageNotFound as exc:
print(f"Page not found: {exc}")
print("exercised: pages.list / pages.get / page_summary.details / PageNotFound")
Lists all published pages on the site. Returns the navigation menu structure with page titles, slugs, links, and modification dates. Single-page response containing every published page.
No input parameters required.
{
"type": "object",
"fields": {
"pages": "array of page summary objects with id, title, slug, link, date, modified",
"total": "integer total number of pages"
},
"sample": {
"data": {
"pages": [
{
"id": 10369,
"date": "2024-12-09T10:35:07",
"link": "https://www.lamomeplage.com/les-restaurants/",
"slug": "les-restaurants",
"title": "Les Restaurants",
"modified": "2026-04-22T15:42:46"
},
{
"id": 4894,
"date": "2022-04-05T13:55:08",
"link": "https://www.lamomeplage.com/nos-cartes/",
"slug": "nos-cartes",
"title": "Nos Cartes",
"modified": "2026-05-27T09:36:14"
}
],
"total": 9
},
"status": "success"
}
}About the Lamomeplage API
Site Structure and Navigation
The list_pages endpoint returns an array of all published pages on the La Môme Plage site. Each page summary object includes a numeric id, title, slug, link, date, and modified timestamp. A total integer tells you how many pages exist. This is useful for discovering available slugs before fetching individual page content.
Page Content Retrieval
The get_page_content endpoint accepts either a slug (e.g., nos-cartes, accueil, les-restaurants, notre-histoire, diners-prives-evenem) or a numeric page_id (e.g., 4894 for Nos Cartes, 9869 for Accueil). If both parameters are supplied, page_id takes precedence. The response includes the page title, slug, link, date, modified, a text_content string with all visible text from the page, an images array of objects with src and alt fields, and a links array of objects with text and url fields.
Coverage Notes
Content is limited to published WordPress pages on the site. The API covers static and editorial content such as menu descriptions, restaurant history, private event details, and location information. Dynamic or transactional data — such as online reservations or real-time availability — is not part of the page content structure.
The Lamomeplage API is a managed, monitored endpoint for lamomeplage.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when lamomeplage.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 lamomeplage.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?+
- Extract full menu text from the
nos-cartespage to display La Môme Plage's offerings in a travel guide app. - Build a restaurant profile card using
title,text_content, andimagesfrom theaccueilornotre-histoirepages. - Enumerate all site pages with
list_pagesto map the restaurant's content structure and detect new pages as the site updates. - Retrieve private dining and events page content to surface venue hire details for event-planning platforms.
- Pull
imagesarrays from restaurant pages to populate a photo gallery component withsrcandaltattributes. - Monitor
modifiedtimestamps vialist_pagesto detect when menu or contact information has been updated. - Aggregate restaurant descriptions and location details for a Cannes dining directory or travel itinerary service.
| 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 La Môme Plage have an official developer API?+
What does `get_page_content` return, and how do I target a specific page?+
id, title, slug, link, date, modified, text_content (all visible text from the page), an images array (each item has src and alt), and a links array (each item has text and url). You can target a page using either its slug (e.g., nos-cartes) or its numeric page_id (e.g., 4894). If both are provided, page_id takes precedence.Does the API return reservation availability or booking data?+
Is there pagination support when listing pages?+
list_pages returns all published pages in a single response along with a total integer. There are no pagination parameters — the full page list is returned at once. If the site's page count grows significantly, response size may increase accordingly.Does the API expose contact details like address or phone number?+
text_content string of relevant pages (such as accueil or les-restaurants) if that text is published on those pages. You can fork the API on Parse and revise it to parse and surface those fields explicitly from text_content.