Discover/The Clumsies API
live

The Clumsies APItheclumsies.gr ↗

Fetch photo gallery image URLs and contact details from The Clumsies cocktail bar in Athens via a single API endpoint with 6 structured fields.

Endpoint health
verified 1h ago
get_gallery
1/1 passing latest checkself-healing
Endpoints
1
Updated
2h ago

What is the The Clumsies API?

The Clumsies API exposes 6 structured response fields from the Athens cocktail bar theclumsies.gr through a single get_gallery endpoint. One call returns the full public photo gallery as an array of image records — each with a full-size URL and a thumbnail URL — plus the bar's street address, phone number, email, and a direct map link from the Find Us section of the site.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/6bbac453-8669-4d29-bf0e-d8725bab6721/<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/6bbac453-8669-4d29-bf0e-d8725bab6721/get_gallery' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 theclumsies-gr-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.

"""Walkthrough: The Clumsies Bar — fetch the photo gallery and contact info."""
from parse_apis.theclumsies_gr_api import TheClumsies, ParseError

client = TheClumsies()

# Fetch the full gallery page: photos + contact details
try:
    gallery = client.gallery.get()
except ParseError as e:
    print(f"Could not load gallery: {e.code}")
    raise

print(f"Address: {gallery.address}")
print(f"Phone:   {gallery.phone}")
print(f"Email:   {gallery.email}")
print(f"Map:     {gallery.map_url}")
print(f"Total images: {gallery.image_count}")

# Browse the first few gallery images
if gallery.images is not None:
    for img in gallery.images[:5]:
        print(img.image_url, "->", img.thumbnail_url)

print("exercised: gallery.get")
All endpoints · 1 totalmissing one? ·

Returns every photo in the site's public Photo Gallery as a list of image records (full-size image URL plus the slider thumbnail URL), together with the bar's contact details shown in the Find Us section (street address, phone, email, map link). One page fetch, no pagination; the gallery is a fixed set (29 images at build time). The site does not publish opening hours anywhere, so opening_hours is always null; it is kept in the payload for forward compatibility only.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "email": "contact email address, or null",
    "phone": "phone text as displayed (e.g. 'T. +30 ...'), or null",
    "images": "array of gallery photos, each with image_url (full-size, absolute) and thumbnail_url (slider thumbnail, absolute; null if absent)",
    "address": "street address text from the Find Us section, or null",
    "map_url": "external map link for the address, or null",
    "image_count": "integer, number of entries in images",
    "opening_hours": "always null — the site publishes no opening hours"
  },
  "sample": {
    "data": {
      "email": "[email protected]",
      "phone": "+1 (555) 012-3456",
      "images": [
        {
          "image_url": "https://www.theclumsies.gr/images/_KO45962.jpg",
          "thumbnail_url": "https://www.theclumsies.gr/images/bg_KO45962.png"
        },
        {
          "image_url": "https://www.theclumsies.gr/images/IMG_0471.JPG",
          "thumbnail_url": "https://www.theclumsies.gr/images/bg11.png"
        }
      ],
      "address": "123 Main St, Springfield, IL 62704",
      "map_url": "https://goo.gl/maps/L99fAcSU44AziDU47",
      "image_count": 29,
      "opening_hours": null
    },
    "status": "success"
  }
}

About the The Clumsies API

What the API Returns

The get_gallery endpoint returns all data available from The Clumsies public website in a single response. The images array contains one record per gallery photo, each with an image_url (absolute, full-size) and a thumbnail_url (absolute slider thumbnail, or null if absent). The image_count field gives the total number of entries in that array without requiring you to count them yourself.

Contact and Location Fields

Alongside the gallery data, the response includes the bar's address (street address text as it appears in the Find Us section), phone (formatted as displayed on the site, e.g. T. +30 ...), email, and map_url (the external map link tied to the address). Any of these can be null if the site does not publish that value at the time of the request.

Pagination and Coverage

The endpoint takes no input parameters and has no pagination — all gallery photos and contact fields are returned in one response. The opening_hours field is always null; The Clumsies does not publish structured hours on the public website, so that field is not populated.

Reliability & maintenanceVerified

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

Last verified
1h ago
Latest check
1/1 endpoint 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
  • Display The Clumsies photo gallery inside a travel or nightlife app using image_url and thumbnail_url fields.
  • Sync bar contact details (address, phone, email) into a venue directory or CRM without manual entry.
  • Generate a location card for The Clumsies using address and map_url in a maps-integrated UI.
  • Monitor changes to the public gallery over time by tracking image_count across periodic calls.
  • Pull full-resolution bar photos for editorial or blog use with direct image_url links.
  • Embed a contact widget for The Clumsies by reading email and phone from the API response.
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 The Clumsies have an official developer API?+
No. The Clumsies (theclumsies.gr) does not publish a public developer API or documented data feed. This Parse API is the only structured programmatic way to access the gallery and contact data the site exposes publicly.
What does `get_gallery` return for each photo?+
Each entry in the images array contains two fields: image_url (the absolute URL of the full-size photo) and thumbnail_url (the absolute URL of the slider thumbnail, or null if no thumbnail is associated with that image). The image_count field at the top level tells you how many entries are in the array.
Are opening hours available from this API?+
Not currently. The opening_hours field is always null because The Clumsies does not publish structured hours on the public page the API covers. The API does return address, phone, email, and map link. You can fork it on Parse and revise it to add an endpoint targeting any other page on the site that may carry hours information.
Can I filter the gallery by photo type or date?+
The get_gallery endpoint returns all photos in the public gallery in one response with no filter parameters. Individual records include image_url and thumbnail_url but no metadata like tags, dates, or categories. You can fork the API on Parse and revise it to add filtering or additional metadata if the source page exposes it.
Does the API return data for multiple venues or locations?+
The API covers only The Clumsies bar at its single Athens location. The response includes one address, one phone number, and one email. You can fork the API on Parse and revise it to pull data from additional venue pages if needed.
Page content last updated . Spec covers 1 endpoint from theclumsies.gr.
Related APIs in Food DiningSee all →