Venues Endpoint

The Venues endpoint provides metadata for the sports venues that are referenced by the sporting event programs.

API and Example Responses

API

http://on-api.gracenote.com/v3/Venues

?updateId=[updateId value]
&limit=[limit value]
&api_key=[your-api-key]

Example Requests

Return full list of venues in batches of 1000:

http://on-api.gracenote.com/v3/Venues?updateId=0&limit=1000&api_key=<your-api-key>

Request Parameters

Parameter	Required?	Description
api_key	Yes	24-character key obtained during application registration
updateId	No	Update token. Defaults to 0. Returns venues beginning with updateId, which is sequential numeric offset received in response.
limit	No	Batch size. Maximum number of venues to be returned by API. Use with updateId.
venueId	No	For non-batch lookups. Comma-separated list of venue IDs. Overrides updateId.

Important: Use lookup calls for QA and troubleshooting purposes only. Gracenote does not support lookup APIs for Client production environments.

Example Responses

Below is an example response. Also see Venues XML example.

Data Structure and Relationships

Venue data is separated into a fixed venue block (containing approximate address) and more dynamic/changeable venueBrand blocks (containing venue name), only one of which is active at a time. This facilitates venue name changes (for example Oracle Arena, Oakland Arena).

Schema

Review the following XML schema definition (xsd) to learn about the data structure, fields, and types for this endpoint.

To explore the relationships among all endpoints, see the interactive schema documentation.

XML Schema URL: http://files.api.gracenote.com/xsd/on_update_venues_3.23.xsd