Discover/Churros con Chocolate API
live

Churros con Chocolate APIchurros-conchocolate.com ↗

Get upcoming party event listings from churros-conchocolate.com via one API endpoint. Returns title, date, time, city, section, and ticket URLs.

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

What is the Churros con Chocolate API?

The Churros con Chocolate API exposes 1 endpoint — list_events — that returns every upcoming event currently published on the site's tickets page, each with 10 structured fields including title, day, month, time, city, section, and a direct ticket purchase URL. It covers events across Barcelona, Madrid, and additional party series, making it straightforward to pull the full listings or filter down to a specific city section in a single call.

This call costs1 credit / call— charged only on success
Try it
Page section to restrict results to. Omitted = all sections.
→ api.parse.bot/scraper/e4c8f5d2-edcb-4b19-a317-1d62d474bae9/<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/e4c8f5d2-edcb-4b19-a317-1d62d474bae9/list_events?section=barcelona' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 1 totalmissing one? ·

Returns every event card currently published on the tickets page in one call (no pagination; the page lists all upcoming events, typically a few per city). Each record is one event with its title, the page section it sits under (Barcelona, Madrid or 'Más Fiestas'), day/month/time as shown on the site (month is a Spanish abbreviation such as 'oct' or 'dic', no year is published), venue name, city label, the external ticket purchase link (third-party ticketing platforms) and the promotional image URL. The optional section filter narrows the result to one page section; an unrecognized section value is rejected. An empty events array for a valid section means that section currently has no cards.

Input
ParamTypeDescription
sectionstringPage section to restrict results to. Omitted = all sections.
Response
{
  "type": "object",
  "fields": {
    "total": "integer count of events returned (after the section filter)",
    "events": "array of event records: title, section, day, month, time, location, city, ticket_url, ticket_label, image_url",
    "page_url": "the source tickets page"
  },
  "sample": {
    "data": {
      "total": 1,
      "events": [
        {
          "day": "25",
          "city": "BCN",
          "time": "16:00",
          "month": "oct",
          "title": "CHURROS – 25 OCT – HALLOWEEN",
          "section": "barcelona",
          "location": "Sala Apolo",
          "image_url": "https://churros-conchocolate.com/wp-content/uploads/2026/08/04_25-oct-300x300.jpg",
          "ticket_url": "https://dice.fm/event/6dogwq-churros-con-chocolate-halloween-25th-oct-sala-apolo-barcelona-tickets",
          "ticket_label": "Entradas"
        }
      ],
      "page_url": "https://churros-conchocolate.com/tickets/"
    },
    "status": "success"
  }
}

About the Churros con Chocolate API

What list_events Returns

The list_events endpoint retrieves all event cards from the Churros con Chocolate tickets page in a single response — no pagination required. Each record in the events array includes the event title, the section it appears under on the page (typically Barcelona, Madrid, or Más Fiestas), the day and month of the event, a time string, the specific location venue, the city, a ticket_url pointing directly to the purchase page, a ticket_label describing the ticketing call-to-action text, and an image_url for the event artwork. The response also includes a total field with the integer count of returned records and a page_url confirming the source page.

Filtering by Section

The endpoint accepts one optional input parameter: section. Pass a string matching one of the page sections (for example, "Barcelona" or "Madrid") to restrict the events array to that group. Omitting the parameter returns all sections combined. The total field reflects the count after any filter is applied, so you can use it directly for display or iteration logic without reprocessing the array.

Coverage and Freshness

The API reflects whatever events are currently listed on the tickets page. Churros con Chocolate publishes a rolling set of upcoming party dates — typically a handful per city at any given time — so the dataset is small but focused. There are no historical or past-event records; only events actively listed on the page at query time are returned.

Reliability & maintenanceVerified

The Churros con Chocolate API is a managed, monitored endpoint for churros-conchocolate.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when churros-conchocolate.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 churros-conchocolate.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.

Last verified
2h 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 a city-specific event calendar filtered by the section parameter for Barcelona or Madrid audiences
  • Monitor for new party dates by polling list_events and diffing against a stored snapshot of title and day fields
  • Build a ticket availability widget that surfaces the ticket_url and ticket_label for each upcoming event
  • Aggregate Churros con Chocolate events alongside other nightlife listings using the city and location fields
  • Power a Telegram or Slack bot that alerts subscribers when new events appear in a specific section
  • Render event artwork in a promotional layout using the image_url field alongside date and venue details
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 Churros con Chocolate have an official developer API?+
No. Churros con Chocolate does not publish a public developer API or data feed. This Parse API is the available programmatic way to access their event listings.
What does the `section` parameter actually filter on?+
It matches the labeled groupings on the tickets page — currently Barcelona, Madrid, and Más Fiestas. Passing one of those strings returns only the events listed under that heading. The total in the response reflects the filtered count. If you pass a value that matches no section, total will be 0 and events will be an empty array.
How many events does a typical response include?+
The site lists a small number of upcoming dates — usually a few events per city section at any time. There is no pagination; all currently published events are returned in a single call. The exact count varies as events are added or removed from the source page.
Does the API return sold-out status or remaining ticket counts?+
Not currently. The API returns ticket_url and ticket_label for each event but does not include sold-out flags, ticket availability counts, or pricing details. You can fork this API on Parse and revise it to add those fields if the source page exposes them.
Are past or historical events included in the response?+
No. The endpoint only reflects events currently listed on the active tickets page. Past events that have been removed from that page are not returned. The API covers only the upcoming events visible at query time. You can fork it on Parse and revise to add an archiving layer if historical tracking is needed.
Page content last updated . Spec covers 1 endpoint from churros-conchocolate.com.
Related APIs in EntertainmentSee all →