Developers

API documentation

A free REST API over the same live data that powers the site. No keys, CORS enabled.

Quick start

curl "https://dropdate.net/api/events?q=ps5 releases next month&limit=2"

{
  "data": [
    {
      "id": "rawg-3498",
      "slug": "example-game",
      "title": "Example Game",
      "kind": "release",
      "start": "2026-11-19",
      "platforms": ["PC", "PlayStation"],
      "genres": ["Action", "RPG"],
      "metacritic": 88,
      "image": "https://media.rawg.io/..."
    }
  ],
  "meta": {
    "total": 14, "limit": 2, "offset": 0,
    "updated": "2026-10-01T12:00:00.000Z",
    "understood": ["Next month", "Releases", "PlayStation"]
  }
}

Endpoints

GET /api/events

Releases and tournaments, sorted by date. Smart search, filters and pagination.

?q=ps5 releases next month&limit=10

GET /api/tournaments

Esports tournaments with prize pools. Same filters as /api/events.

?q=this week

GET /api/games

Full details for one game: description, developers, trailer, screenshots, stores.

?slug=cyberpunk-2077

GET /api/calendar.ics

Subscribable iCalendar feed. Same filters as /api/events, or ?ids=a,b for specific events.

?type=release&q=xbox

Parameters

q: Smart search: plain English plus game names (typo tolerant)
type: release | tournament
platform: PC | PlayStation | Xbox | Nintendo | Mobile
genre: One genre, e.g. RPG or Shooter
past: true to list events that already happened
limit / offset: Pagination. limit defaults to 50, max 200

Smart search

The q parameter understands types (releases, tournaments, esports), platforms (pc, ps5, xbox, switch, mobile) and time (today, this weekend, next 30 days, next month, oct, q4, in the summer, 2027, past). Months can be abbreviated, half typed or misspelled. Anything left over is a typo-tolerant search on titles and genres (fps and mmo work too). meta.understood shows how your query was read.

/api/events?q=esports this week
/api/events?q=nintendo in december
/api/events?q=zelda

Freshness & fair use

Data refreshes automatically every hour and responses are cached at the edge. Please cache on your side too and keep request rates reasonable.