Each performer should have their own “landing page” which includes information about that performer and shows any upcoming Events for that performer. Because the Ticket Evolution catalog includes over 45000 Performers, these pages are dynamically created and usually use the slug
property of the Performer to create the URL. In the case of the Arizona Diamondbacks the slug
is arizona-diamondbacks
and your URL might look something like www.myawesometicketsite.com/arizona-diamondbacks-tickets
To generate such a page you should retrieve the Performer slug
from the URL, which in the example of www.myawesometicketsite.com/arizona-diamondbacks-tickets would be arizona-diamondbacks
. Then two API requests are made, the first one being Performers / Show in order to retrieve information about the performer.
curl -i \ -X GET \ -H "X-Signature: Eha/EE1EbP8mYqmf72AYOq0ee641Y/Q6EoRgDGv1+zM=" \ -H "X-Token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \ --url 'https://api.ticketevolution.com/v9/performers/arizona-diamondbacks?'
$response = $client->showPerformer([ 'performer_id' => 'arizona-diamondbacks', ]);
@performer = @connection.performers.show('arizona-diamondbacks')
After making the Performer / Show API request the id
of the Performer (15556 in this example) can be used to display upcoming Events using the Events / Index endpoint.
curl -i \ -X GET \ -H "X-Signature: oy8oDMMfSjCoz6R3oWsE5/2CsKYlypgnHbL9YtDLUAo=" \ -H "X-Token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \ --url 'https://api.ticketevolution.com/v9/events?page=1&per_page=2&performer_id=15556'
$response = $client->listEvents([ 'performer_id' => (int)15556, ]);
@event = @connection.events.list({ 'performer_id' => 15556 })
Previous: XXX
Next: YYY