What’s the story, Dublin?

Events API

Upcoming public events in Dublin for the next 30 days, for apps, student projects and community tools.

• Addresshttps://whatsthestorydublin.ie/api/v1
• AccessFree API key, by email
• Limits60 a minute, 2,000 a day
• UpdatedOnce or twice a day

Quick start

1. Get a key. Email hello@whatsthestorydublin.ie with your name, what you’re building and roughly how often you’ll call the API.
2. Ask for some events. Send the key in an Authorization header, from your server. Never put it in a website or app, where anyone could copy it.

   curl -G "https://whatsthestorydublin.ie/api/v1/events" \
     -H "Authorization: Bearer YOUR_KEY" \
     -d from=2026-11-14 -d to=2026-11-15 \
     -d tag=Music,Comedy \
     -d limit=5

3. Read the reply. Events come in start-time order, one page at a time. Follow links.next for the next page; it’s null on the last one.

   {
     "data": [
       {
         "id": "3dce71a0-…",
         "title": "Example Gig",
         "start": "2026-10-24T19:30:00.000Z",
         "end": "2026-10-24T22:30:00.000Z",
         "all_day": false,
         "status": "available",
         "category": "Music",
         "tags": ["Music", "Jazz"],
         "is_free": false,
         "price": "€15",
         "venue": { "name": "Example Venue", "area": "City Centre South", … },
         "source_url": "https://example-venue.ie/whats-on/example-gig",
         …
       }
     ],
     "meta": {
       "total": 214, "limit": 5,
       "has_more": true, "next_cursor": "eyJ2Ijox…"
     },
     "links": { "next": "https://whatsthestorydublin.ie/api/v1/events?…" },
     "attribution": { "text": "Event data from What's the story, Dublin?", … }
   }

Endpoints

Both event endpoints also take fields, to return only what you need.

Filters for /v1/events

Combine any of these. Unknown or repeated parameters are refused with a 400, so a typo can’t quietly return the wrong events.

A page link keeps working even if events are added or removed between pages. Keep the same filters when you pass a cursor.

Fields

New fields may appear at any time. Ignore the ones you don’t recognise.

Errors and limits

Our errors look like {"error": {"code", "message", "request_id"}}. Quote the request_id if you report a problem. 401 and 429 come from our gateway in the standard application/problem+json shape instead.

Limits per key: 60 requests a minute and 2,000 a day.

Using the data well

Suggestions, not rules. The rules are in the terms.

• Refresh once a day, and drop events that disappear. Events leave the feed when they end, are cancelled or are taken down. The data changes once or twice a day, so checking more than hourly gains nothing.
• Send the ETag back as If-None-Match. When nothing changed you get an empty 304, which doesn’t count towards your daily limit.
• Link each event to its source_url. The organiser’s page has the full details and tickets.
• Show the status. Label cancelled, postponed and sold-out events rather than leaving them looking available.
• Ask only for what you need with fields, and use the largest limit you can handle to make fewer requests.

Changes

Version 1 only grows: new fields, filters and endpoints, never removals or renames. If we ever have to break something, it will be a new /v2 address, and /v1 will keep running for at least six months after we email key holders.