Events

Events at a venue

Every launch-org event held (or booked) at one venue, newest first — upcoming cards on top, then the history. Same filters and row shape as /v1/events (status, from, to, order, cursor pagination); order=asc reverses it. meta.venue names the venue. An unknown venue, or one with no covered event at this venue (a staged-org-only arena), 404s not_found.

get/v1/venues/{id}/events

Request

  • Base URL: https://api.ufcalendar.com
  • URL: https://api.ufcalendar.com/v1/venues/{id}/events
  • Auth: HTTP bearer

Path parameters

idinteger required

Query parameters

status'announced' | 'scheduled' | 'live' | 'completed' | 'cancelled' | 'postponed' | 'upcoming'

What ?status= accepts on the event lists: every EventStatus, plus upcoming = announced, scheduled or live cards that have not finished (the site's upcoming-or-live window: started under 6 h ago, or under 14 h ago with a bout still to fight). upcoming is a filter only — it never appears on an event.

Same values as /v1/events; upcoming = the venue's cards not yet over.

fromstring date

First UTC calendar day, inclusive YYYY-MM-DD, matched against the event's starts_at (first bell, UTC) — not the venue's local date. Must be a real calendar day.

tostring date

Last UTC calendar day, inclusive YYYY-MM-DD, matched against starts_at (UTC). An evening card in the Americas starts after midnight UTC, so it falls on the next UTC day: a Saturday-night Las Vegas card needs to= the Sunday. Must be a real calendar day.

order'asc' | 'desc'
cursorstring

Opaque cursor from meta.pagination.next_cursor.

limitinteger

Response

Events at the venue

Example response

{
  "data": [
    {
      "sport": "mma"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.