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.

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 titlename on /v3/events searches event titles (festival names, special-billing show titles), resolved against the JamBase title-search index.
  • Events by who or whereartistName and venueName on /v3/events narrow events to a performer or venue by name.
  • ArtistsartistName on /v3/artists finds artist records by name.
  • VenuesvenueName on /v3/venues finds venue records by name.

Parameters by endpoint

Which name parameter applies where, and what else the endpoint requires.

EndpointName parameterSearchesRequired with
GET /v3/eventsnameEvent titlesNothing — optional filter
GET /v3/eventsartistNameEvents by performer nameNothing — optional filter
GET /v3/eventsvenueNameEvents at a venue by nameNothing — optional filter
GET /v3/artistsartistNameArtist recordsAt least one of artistName or genreSlug
GET /v3/venuesvenueNameVenue recordsvenueName 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 Bowl can return more than one venue. For an exact record, prefer an ID or slug (see below).
  • Filters combine as AND. A name parameter narrows the same result set every other parameter narrows. name=Phish New Year combined with geoCityId returns only matching events in that city.
  • Multiple values use a pipe. artistName=Billie Eilish|Lucy Dacus matches either. The same pipe form works for venueName.
  • 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 200 with an empty array and totalItems: 0.
  • Title search fails soft. If the title-search tier is briefly unavailable, name is treated as no match (empty list) — never a 5xx.
  • artistName is ignored when artistId is 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=Phish%20New%20Year&geoCityId=jambase:4223296" \