Search
Resolve a free-text name into matching events, artists, or venues. Keyword search is a filter on the core feeds — it narrows the same result set every other parameter narrows, so it composes with dates, locations, and IDs.
What you can search
Three families accept a keyword name search; each has its own parameter.
JamBase Data exposes keyword search as a set of name parameters on the core search endpoints — there is no separate /search endpoint. You search by adding the right name parameter to the feed you already query:
- Events by title —
nameon/v3/eventssearches event titles (festival names, special-billing show titles), resolved against the JamBase title-search index. - Events by who or where —
artistNameandvenueNameon/v3/eventsnarrow events to a performer or venue by name. - Artists —
artistNameon/v3/artistsfinds artist records by name. - Venues —
venueNameon/v3/venuesfinds venue records by name.
Streams have no name search
/v3/streams filters by date and source only — there is no keyword name parameter for streams. To find an artist’s streams, resolve the artist first and follow their upcoming streams.Parameters by endpoint
Which name parameter applies where, and what else the endpoint requires.
| Endpoint | Name parameter | Searches | Required with |
|---|---|---|---|
GET /v3/events | name | Event titles | Nothing — optional filter |
GET /v3/events | artistName | Events by performer name | Nothing — optional filter |
GET /v3/events | venueName | Events at a venue by name | Nothing — optional filter |
GET /v3/artists | artistName | Artist records | At least one of artistName or genreSlug |
GET /v3/venues | venueName | Venue records | venueName or at least one geo parameter (geoCityId, geoMetroId, geoStateIso, geoCountryIso2, …) |
How results behave
The rules are the same across every name parameter.
- Keyword, not exact-match. Name search is a keyword lookup, so
venueName=Brooklyn Bowlcan return more than one venue. For an exact record, prefer an ID or slug (see below). - Festival names on past windows match by leading words. With
eventType=festivalsand a past or open-ended date window,name=Camp Flog Gnawalso finds "Camp Flog Gnaw Carnival" when no festival is named exactly that. An exact name always wins. A window that starts in the past and runs into the future returns past editions and upcoming matches together. A festival name that matches nothing returns an empty list; it is not retried as an artist name. - Filters combine as AND. A name parameter narrows the same result set every other parameter narrows.
name=New Year's Evecombined withgeoCityIdreturns only matching events in that city. - Multiple values use a pipe.
artistName=Billie Eilish|Lucy Dacusmatches either. The same pipe form works forvenueName. - URL-encode your keywords. Spaces become
%20; the pipe may stay literal or be encoded as%7C. - No match returns an empty list, not an error. You get a well-formed
200with an empty array andtotalItems: 0. - Title search fails soft. If the title-search tier is briefly unavailable,
nameis treated as no match (empty list) — never a5xx. artistNameis ignored whenartistIdis present. ID filters always win over the keyword form on the same family.- Results page like any other feed. Use
page/perPage(max 100) — see Pagination.
Worked examples
Copy-paste curl for each name parameter.
Find a festival by title
curl "https://api.data.jambase.com/v3/events?name=Bonnaroo" \-H "Authorization: Bearer YOUR_API_KEY"
Find an artist’s upcoming events by name
curl "https://api.data.jambase.com/v3/events?artistName=Billie%20Eilish" \-H "Authorization: Bearer YOUR_API_KEY"
Combine a title search with a location filter
curl "https://api.data.jambase.com/v3/events?name=New%20Year%27s%20Eve&geoCityId=jambase:4223296" \-H "Authorization: Bearer YOUR_API_KEY"
Search artist records
curl "https://api.data.jambase.com/v3/artists?artistName=Lucy%20Dacus" \-H "Authorization: Bearer YOUR_API_KEY"
Search venue records
curl "https://api.data.jambase.com/v3/venues?venueName=Brooklyn%20Bowl" \-H "Authorization: Bearer YOUR_API_KEY"
Match several names at once
curl "https://api.data.jambase.com/v3/events?artistName=Billie%20Eilish|Lucy%20Dacus" \-H "Authorization: Bearer YOUR_API_KEY"
When to search vs. look up
Keyword search is for discovery; IDs and slugs are for precision.
Reach for name search when you have a human-typed string and want candidates. Once you know the exact record — or you already hold a third-party identifier — switch to an ID or slug for a single, unambiguous result:
- Use
artistId/venueId/eventId(orartist[slug]/venue[slug]) on the search endpoints for exact filtering. - If you hold a Spotify, Ticketmaster, MusicBrainz, or SeatGeek ID, skip search entirely and use Reverse ID Lookup to resolve straight to the JBD object — no fuzzy name matching.
Related
- Reverse ID Lookup — resolve a third-party ID straight to the JBD object
- Bulk Ingest & Delta Sync — seed a local cache and keep it fresh
- Deleted Items — tombstones that signal a record left the catalog
- API Reference — full parameter listing per endpoint
Last updated May 1, 2026