Search Upcoming Streams

Page number of results to retrieve

Number of events per page of results

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.

Filter streams to those sourced from a specific stream platform.

v3 currently exposes a single source slug — jambase — which represents JamBase's normalized stream catalog. Pipe-delimited values are supported for forward compatibility:

• streamDataSource=jambase

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.