Search Performers

one or more performer ids to search. (ie. id=123 |456) NOTE: there is a space between the ID and the | but no space between the ID following the | delimeter. The limit for all the ids is 200

search by keyword

search by performer name

filter by grouping id (including children grouping if any), data type is long. secondary grouping id was also included.

filter by grouping name(including children grouping if any), data type is string.

search by categoryId for example to filter concert categories (1) and NOT festivals (490277): cateegoryId=1 -490277

search by categoryName

The status of the performer. Valid statuses are: Active, Inactive, Deleted, Draft, Review, Closed, Restricted

Spatial search by lat-lon and radius, data type is String, lat-long is concated using comma, e.g. point=34.7452778,-92.3275

spatial search by lat-lon and radius, data type is double. e.g. 20 or 32.1869

radius units, supported values: mi, km

If need to include hidden performers, value will be true of false. true means include hidden performers

Performer external source, supported values: spotify, itunes, zvents, rovi, mediaNet,amg, espn, Worked with id together

return results starting from the specified index.

max results to return, max=500.

Performer Provider. Supported values -1-All, 0-Unified,1-StubHub,2-Zvents,3-MediaNet,4-AMG

If need to use image randomization, value will be true or false, true means to use image randomization

**Optional Parameter**. A pair of space-separated tokens that specifies how the performers are sorted. - First token identifies property of the performer for sorting. For the first token, you can specify any one of the following properties: `name`, `status`, `popularity`, `localPopularity`, `distance`,`createdDate` , `eventCount` - Second token specifies the direction of the sort. For the second token, you can specify one of the following types - `asc` for ascending order, `desc` for descending order Syntax: `property asc` or `property desc` If you do not provide this parameter. the default is the listings are sorted by name in ascending order (`sort=name asc`) You can also sort multiple fields with a statement like this: `sort=name asc, popularity desc` Examples: - Single Value Sort: `sort=name desc` to sort the performer in their descending order of name. - Multiple Values Sort: `sort=name asc, popularity desc, eventCount asc` In this example, the parameters are sorted in the following order: - By name (in ascending order); - If any performer have the same name, then they are sorted by popularity (in descending order); - If any performer are identical in both name and popularity, then they are sorted by the eventCount (in ascending order).

The list of fields to be displayed in the response. This parameter can be used if you would like to fetch only a subset of the default response. Allowed values are: numFound, id, status, name, description, url, categories, groupings, ancestors, aliases, displayAttributes, popularities, images, eventCount, score, createdDate, distance, performerAttributes, catalogAttributes

To generate an access token, use the [generateToken API](https://developer.stubhub.com/oauth/apis/post/accesstoken). Note that you will need to add a 'Bearer ' prefix to your access token. Otherwise, you'll get an 'Invalid Access Token' error

application/json