Quickstart

Create a key, make a call, read the response. About a minute.

1. Get a key

Sign in at edmdb.net/account/developer.
Choose Create API key, give it a name you will recognise later, and copy the key.

The key is shown once

Keys are stored hashed, so we cannot show one to you again. If you lose it, revoke it and create another — there is no recovery path, by design.

2. Make a call

Every request needs your key. Upcoming events, ten at a time:

curl

curl -s "https://developer.edmdb.net/api/v1/events?limit=10" \
  -H "Authorization: Bearer edm_live_..."

3. Read the response

List endpoints return a data array and a page object. Nothing is ever omitted for being empty — an absent value is null, so you can destructure without guards.

200 OK

{
  "data": [
    {
      "id": "…",
      "slug": "afterlife-amsterdam-2026",
      "name": "Afterlife — Amsterdam",
      "start_at": "2026-08-15T20:00:00.000Z",
      "end_at": null,
      "timezone": "Europe/Amsterdam",
      "status": null,
      "venue": {
        "slug": "warehouse-elementenstraat",
        "name": "Warehouse Elementenstraat",
        "city": "Amsterdam",
        "country": "NL"
      },
      "url": "https://edmdb.net/events/afterlife-amsterdam-2026"
    }
  ],
  "page": { "next_cursor": "eyJ…", "has_more": true }
}

Where to go next

The API reference lists every endpoint and lets you call them from the browser. Pagination covers walking past the first page, and Errors covers what to do when a call fails. If you want EDMDb inside an AI assistant instead, see the MCP server.

A note on where the API stands

The read endpoints are live and stable in shape. Per-tier quotas are not enforced yet, so the limits on pricing are not being applied — see rate limits for what actually governs your key today.