Search Events

Page number of results to retrieve

Number of events per page of results

Used to isolate only concerts or only festivals(s)
Leave blank to include both concerts and festivals

• eventType=concert
• eventType=festival

Restrict the result set to a specific list of Event IDs.

For example to fetch a single event:

• eventId=jambase:16013248

Use a pipe (|) to include multiple event IDs (recommended form, consistent with artistId and venueId):

• eventId=jambase:16013248|jambase:14331594

A URL-encoded JSON array of IDs is also accepted for compatibility with the v1 eventId parameter:

• eventId=%5B%22jambase%3A16013248%22%2C%22jambase%3A14331594%22%5D

To use non-JamBase data sources, use the EventDataSource [enum] for the ID(s) you are using.

Keyword search that matches event and festival titles.

• name=Bonnaroo
• name=New%20Year%27s%20Eve

Combines as AND with any other filters (artistId, geoCityId, dates, etc.). No match returns an empty list — never an error.

Also works on past windows (with expandPastEvents=true and/or a past eventDateFrom, subject to your plan's past-events access): festival names resolve to their historical editions (e.g. name=Coachella with a 2024 window), and other names match as an artist keyword. Venue names and one-off show titles are not matched on past windows — use venueName / venueId for past venue timelines.

The source and unique identifier for the artist(s).

For example to search for LCD Soundsystem events:

• artistId=jambase:228924

Use a pipe (|) to include multiple artist IDs.

For example to search for LCD Soundsystem & Khalid events:

• artistId=jambase:228924|jambase:3074545

To use non-JamBase data sources, use the ArtistDataSource [enum] for the ID(s) you are using.

For example to search for LCD Soundsystem events using their Ticketmaster ID:

• artistId=ticketmaster:K8vZ9175st0

A keyword-based search for artist name(s).

• artistName=Billie%20Eilish

Use a pipe (|) to include multiple artist names.

• artistName=Billie%20Eilish|Lucy%20Dacus

Keywords should be URL Encoded.
For more precise artist-specific results try using artistId or artist[slug].

Please note that artistName cannot be used togehter with artistId type searches and will be ignored if artistId is provided.

Restrict results to a genre.

• genreSlug=bluegrass

Use a pipe (|) to include results from multiple genres.

• genreSlug=bluegrass|blues

The source and unique identifier for the venue(s)

• venueId=jambase:62108

Use a pipe (|) to include multiple venue IDs

• venueId=jambase:62108|jambase:7932731

To use non-JamBase IDs, use the <a href="https://data.jambase.com/api/reference/get-venue-data-sources">source slug</a> for the ID(s) you are using

• venueId=ticketmaster:k7vGF99ORYpnS

A keyword-based search for venue name(s).

• venueName=Brooklyn%20Bowl

Use a pipe (|) to include multiple venue IDs.

• venueName=Brooklyn%20Bowl|House%20of%20Blues

For more precise venue-specific results try using venueId or venue[slug].

Use to retrieve events for specific <a href="https://data.jambase.com/api/reference/search-cities">JamBase city ID(s)</a> .

• geoCityId=jambase:4223296

Use a pipe (|) to include multiple city IDs.

• geoCityId=jambase:4223296|jambase:4224564

When using the geoCityId parameter, you can omit the the geoRadiusAmount parameter (or) set it to 0 (or) leave it empty to include only results from the city. Else, you can use a radius amount to include events within a radius around the city-center.

The two-letter ISO 3166-1 alpha-2 code for a country.

• geoCountryIso2=US

Use a pipe (|) to include multiple countries.

• geoCountryIso2=US|CA

Geographic filters alone request the normal upcoming-events dataset, even on historically entitled subscriptions; dateModifiedFrom alone is not historical intent either. On plans with geo + historical search (Enterprise baseline, or granted by request), request history explicitly with a licensed past event-date window or expandPastEvents=true. For country-by-country historical backfills, prefer bounded eventDateFrom/eventDateTo windows with no expand flag needed. An authorized historical request with no lower event-date bound receives the later fixed subscription date and rolling plan/override floor before origin fetch; truly unlimited history gets no invented floor. Iterate only countries that actually have data for your target date range (ask support for the coverage list) rather than sweeping every ISO code. Note the code for the United Kingdom is GB, not UK — source data occasionally shows UK, but this filter expects GB.

The three-letter ISO code for a country.

• geoCountryIso3=USA

Use a pipe (|) to include multiple countries.

• geoCountryIso3=USA|CAN

Use to retrieve events near an IP address.
Supports IPv4 or IPv6 values.

• geoIp=55.123.456.789

The latitude for geographic radius.

• geoLatitude=40.7505

The longitude for geographic radius.

• geoLongitude=-73.9934

Use to retrieve events for specific <a href="https://data.jambase.com/api/reference/get-metros">metro ID(s)</a>.

• geoMetroId=jambase:1

Use a pipe (|) to include multiple metro IDs.

• geoMetroId=jambase:1|jambase:5

The search radius for lat/lng type searches.

• geoRadiusAmount=60

Whether to use miles (default) or kilometers for radius.

• geoRadiusUnits=km

The State code in ISO_3166-2 format [docs].

• geoStateIso=US-NY

Use a pipe (|) to include multiple State codes.

• geoStateIso=US-NY|=US-PA

Note: Available for United States, Canada, and Australia only.

Use a dynamic date preset.

• eventDatePreset=tomorrow

Notes:

• The eventDatePreset will override eventDateFrom & eventDateTo if those are set as well.
• The halloween preset returns events on 10/31 only. The newYears preset returns events on 12/31 only. The july4th preset returns events on or near July 4th.

For concerts must start on or after this date.
For festivals, must start on or after this date.
If left blank or omitted, will use the current date.

• eventDateFrom=2023-10-31

Using a date before the current date requires historical access:

• On plans with geo + historical search (Enterprise baseline, or granted by request), send a past eventDateFrom (and optionally eventDateTo) together with any geo parameter such as geoCountryIso2. No expand flag is needed; historical intent is inferred from the date range. Requests beyond the 5,000/day per-subscription allowance fall back to the standard search path and set the X-JBD-Geo-Historical-Fallback response header (check it during backfills).
• On other plans with historical access, combine expandPastEvents=true with artistId or venueId for a single artist or venue timeline (window depends on plan).

Note: Dates use <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC3339</a> format.

For concerts must start on or before this date.
For festivals must end on or before this date.
If left blank or omitted, will return all events after eventDateFrom.

• eventDateTo=2023-12-31

For historical queries, pair with a past eventDateFrom (see that parameter for the per-plan access patterns).

Note: Dates use <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC3339</a> format.

The EventDataSource of for the Event.

Must have been updated on or after this dateTime in GMT.
If left blank or omitted, will use all updated on dates

• dateModifiedFrom=2022-10-31 00:00:00

On its own, a dateModifiedFrom sweep only returns events whose dates have not yet passed — modifications to past-dated events never appear in a plain delta sweep. To catch changes to past shows, plans with geo + historical search (Enterprise baseline, or granted by request) can combine dateModifiedFrom with a geo parameter (such as geoCountryIso2) and an explicit past eventDateFrom/eventDateTo range. Two caveats: the historical index refreshes on a delay (up to about a day), so overlap historical watermarks by 24-48 hours; and a response carrying the X-JBD-Geo-Historical-Fallback header was served without past events and should be re-run after the UTC day resets.

Removal rows (tombstones carrying deletionStatus) are appended to delta sweeps. A delta filtered by artistId or venueId carries only the removal rows for events that had that artist in the lineup or were at that venue when removed, and its totals count only those. Removals with no recorded artist or venue (mostly from before 2026-10-29) and slug/name-filtered deltas carry none; to see every removal, run one unfiltered dateModifiedFrom sweep or use the 400 identifier_invalid lookup fallback.

Note: Use <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC3339</a> format for parameter values.

Must have been first published on or after this dateTime in GMT.

If left blank or omitted, will use all first published on dates.

• datePublishedFrom=2022-01-01 00:00:00

Note: Use <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC3339</a> format for parameter values.

Use true to include external IDs for Concert, Artist, and Venue objects.
Note: expandExternalIdentifiers is included on Startup and higher plans and on Trial. Looking up a record by a third-party ID (for example /v3/artists/id/spotify:{id}) works on every plan; see Reverse ID Lookup.

Use true to include sameAs (i.e. links) for Artist responses.
Note: expandArtistSameAs is included on Startup and higher plans and on Trial. Looking up a record by a third-party ID (for example /v3/artists/id/spotify:{id}) works on every plan; see Reverse ID Lookup.

Use true to explicitly request past/historical Concert and Festival objects.
On entity-scoped historical access, including standard Pro, combine it with one of the six accepted scope selectors: artistId, artistSlug, artistName, venueId, venueSlug, or venueName. Requests without a scope selector are denied with a 403 explaining how to correct the request. An explicit all-scope entitlement removes that gateway scope requirement, but the request remains subject to endpoint validation and its independent historical window.
Note: dateModifiedFrom is a modification-date filter, not an entity scope or request for history, and cannot substitute for a scope selector.
Availability is tiered by plan: Trial and the free MCP plan get a rolling 1-year window, Pro a rolling 3-year window (artist/venue lookups only), and Pro+ and Enterprise include all-scope access with the full archive. Scope and time window are independent contract dimensions: a per-subscription all-scope grant widens which queries may use history but does not change that subscription's historical window.
On plans with geo + historical search (Enterprise baseline, or granted by request), a licensed past event-date window together with any geo parameter such as geoCountryIso2 is sufficient, with no expand flag needed. This flag is also accepted as explicit historical intent on an entitled geo request. Geo filters alone return normal upcoming events. When an authorized historical request omits its lower event-date bound, the gateway forwards its effective fixed-plus-rolling historical floor before fetching; truly unlimited history receives no invented floor.

Sort order for the returned events. \

• eventDate — ascending by event date (oldest first). This is the default. \
• -eventDate — descending by event date (most recent first).
  The leading - indicates descending order, following the JSON:API convention.
  Most useful when combined with expandPastEvents=true to retrieve an artist's or venue's most recent shows first without paginating through their full history.

Use true to suppress the performer node in Concert and Festival objects.