<commit_before>---
layout: documentation-single
categories:
- documentation
- getting-started
---


#GETTING STARTED


{: .lead .double-margin}
Everything you need to start playing with the Ticketmaster APIs.

{: #introduction}
##Introduction


{: .body}
Welcome to the Ticketmaster API! To get you started, we'll go over the **live events core datasets** we’ve made
available to you. Once you [register for a key](https://dev-livenation.devportal.apigee.com/user/login), you will
be able to access the following datasets:

{: .double-margin}
|Dataset            |  Description                                                                                              |
|:------------------|:----------------------------------------------------------------------------------------------------------|
|Events             |A live event must have a date, time, venue and attaction associated with it. Sometime the venue is TBD     |
|Venues             |A venue is a physical location at which an event takes place. A venue can also has sub-venues (rooms).     |
|Attractions        |Any event should have at least one attraction. Artists, teams, stand-up comics are examples of attractions.|
|Offers             |Offers are generally event-specific. Sometimes special offers are applied to carts or to particular API keys.  |
|Tickets            |Any particular offer can hold a variety of tickets. A ticket is transactable.                              |
|Cart               |A cart can hold any transactable item, like tickets, merchandize, parking, etc.                         |


These datasets are distributed across four distinct APIs: Discovery API, Commerce API, Accounts API and Orders API.

{: .body .double-margin-bottom}
This overview covers the core concepts that you need to know before you could 
fully use the APIs to their potential. Once you have a good understanding of the
API core concepts, you can then dig deeper into each API by visiting its 
dedicated overview page.

{: .double-margin #uri-format}
## URI Format

All API calls follow this format: 

_https://app.ticketmaster.com/{package}/{version}/{resource}.json?apikey=**{API key}_
{: .code .red}

<table class="tableParametrs">
	<tr>
		<th>Name</th>
		<th>Description</th>
		<th>Required?</th>
		<th>Default Value</th>	
	</tr>
	
	<tr>
		<td>
			<code>package</code>
		</td>
		<td>A bucket that provides access to logically-related resources</td>
		<td><strong>Yes</strong></td>
		<td>
			<span class="text-info">discovery, commerce, accounts, etc</span>
		</td>
	</tr>
	
		<tr>
		<td>
			<code>version</code>
		</td>
		<td>The package version</td>
		<td><strong><strong>Yes</strong></strong></td>
		<td>
			<span class="text-info">v1, v2, v3, etc</span>
		</td>
	</tr>
	
	<tr>
		<td>
			<code>resource</code>
		</td>
		<td>Path to API method</td>
		<td><strong>Yes</strong></td>
		<td>
			<span class="text-info">Varies per API call</span>
		</td>
	</tr>

	<tr>
		<td>
			<code>API key</code>
		</td>
		<td>Authorized API Key</td>
		<td><strong>Yes</strong></td>
		<td>
			<a class="standart-btn" href="https://dev-livenation.devportal.apigee.com/user/login" title="Get your API key">Get your API key</a> 
		</td>
	</tr>

</table>

### URI Examples

https://app.ticketmaster.com/discovery/v1/events.json?apikey=<KEY>
{: .code .red}

http://app.ticketmaster.com/discovery/v1/events.json?keyword=Madonna&apikey=4dsfsf94tyghf85jdhshwge334&callback=myFunction
{: .code .red}

https://app.ticketmaster.com/commerce/v1/events/434343434/offers.json?apikey=<KEY>
{: .code .red}

{: .double-margin #rate-limit}
## Rate Limit

All API keys are issued with a _default quota_ of **5000 API calls/day**. We do increase rate limits on case-by-case basis. In order to increase the rate limit for a particular application, we need to verify the following:

1. The application is in compliance with our [Terms of Service](/support/terms-of-use/)
2. The application is in compliance with our branding guide
3. The application is representing the Ticketmaster data properly

You can see how much of your quota has been used by checking the following **response headers**:

* Rate-Limit:
* Rate-Limit-Available:
* Rate-Limit-Over:
* Rate-Limit-Reset:

{: .code .red}
	curl -I 'http://app.ticketmaster.com/discovery/v1/events.json?keyword=Queen&apikey=xxx'

	HTTP/1.1 200 OK
	Access-Control-Allow-Headers: origin, x-requested-with, accept
	Access-Control-Allow-Methods: GET, PUT, POST, DELETE
	Access-Control-Allow-Origin: *
	Access-Control-Max-Age: 3628800
	Content-Length: 10125
	Content-Type: application/json;charset=UTF-8
	Date: Mon, 18 Jan 2016 05:59:31 GMT
	Rate-Limit: 5000
	Rate-Limit-Available: 4978
	Rate-Limit-Over: 0
	Rate-Limit-Reset: 1453180594367<commit_msg>Updating CSS<commit_after>---
layout: documentation-single
categories:
- documentation
- getting-started
---


#GETTING STARTED


{: .lead .double-margin}
Everything you need to start playing with the Ticketmaster APIs.

{: #introduction}
##Introduction


{: .body}
Welcome to the Ticketmaster API! To get you started, we'll go over the **live events core datasets** we’ve made
available to you. Once you [register for a key](https://dev-livenation.devportal.apigee.com/user/login), you will
be able to access the following datasets:

{: .double-margin}
|Dataset            |  Description                                                                                              |
|:------------------|:----------------------------------------------------------------------------------------------------------|
|Events             |A live event must have a date, time, venue and attaction associated with it. Sometime the venue is TBD     |
|Venues             |A venue is a physical location at which an event takes place. A venue can also has sub-venues (rooms).     |
|Attractions        |Any event should have at least one attraction. Artists, teams, stand-up comics are examples of attractions.|
|Offers             |Offers are generally event-specific. Sometimes special offers are applied to carts or to particular API keys.  |
|Tickets            |Any particular offer can hold a variety of tickets. A ticket is transactable.                              |
|Cart               |A cart can hold any transactable item, like tickets, merchandize, parking, etc.                         |


These datasets are distributed across four distinct APIs: Discovery API, Commerce API, Accounts API and Orders API.

{: .body .double-margin-bottom}
This overview covers the core concepts that you need to know before you could 
fully use the APIs to their potential. Once you have a good understanding of the
API core concepts, you can then dig deeper into each API by visiting its 
dedicated overview page.

{: .double-margin #uri-format}
## URI Format

All API calls follow this format: 

_https://app.ticketmaster.com/{package}/{version}/{resource}.json?apikey=**{API key}_
{: .code .red}

<table class="tableParametrs">
	<tr>
		<th>Name</th>
		<th>Description</th>
		<th>Required?</th>
		<th>Default Value</th>	
	</tr>
	
	<tr>
		<td>
			<code>package</code>
		</td>
		<td>A bucket that provides access to logically-related resources</td>
		<td><strong>Yes</strong></td>
		<td>
			<span class="text-info">discovery, commerce, accounts, etc</span>
		</td>
	</tr>
	
		<tr>
		<td>
			<code>version</code>
		</td>
		<td>The package version</td>
		<td><strong><strong>Yes</strong></strong></td>
		<td>
			<span class="text-info">v1, v2, v3, etc</span>
		</td>
	</tr>
	
	<tr>
		<td>
			<code>resource</code>
		</td>
		<td>Path to API method</td>
		<td><strong>Yes</strong></td>
		<td>
			<span class="text-info">Varies per API call</span>
		</td>
	</tr>

	<tr>
		<td>
			<code>API key</code>
		</td>
		<td>Authorized API Key</td>
		<td><strong>Yes</strong></td>
		<td>
			<a class="standart-btn" href="https://dev-livenation.devportal.apigee.com/user/login" title="Get your API key">Get your API key</a> 
		</td>
	</tr>

</table>

### URI Examples

https://app.ticketmaster.com/discovery/v1/events.json?apikey=<KEY>
{: .code .red}

http://app.ticketmaster.com/discovery/v1/events.json?keyword=Madonna&apikey=4dsfsf94tyghf85jdhshwge334&callback=myFunction
{: .code .red}

https://app.ticketmaster.com/commerce/v1/events/434343434/offers.json?apikey=<KEY>
{: .code .red}

{: .double-margin #rate-limit}
## Rate Limit

All API keys are issued with a _default quota_ of **5000 API calls/day**. We do increase rate limits on case-by-case basis. In order to increase the rate limit for a particular application, we need to verify the following:

1. The application is in compliance with our [Terms of Service](/support/terms-of-use/)
2. The application is in compliance with our branding guide
3. The application is representing the Ticketmaster data properly

You can see how much of your quota has been used by checking the following **response headers**:

* **Rate-Limit**: What's the rate limit available to you. The default is 5000.
* **Rate-Limit-Available**: How many requests are available to you. This will be 5000 minus all the requests you've done.
* **Rate-Limit-Over**: How many requests over your quota you've made.
* **Rate-Limit-Reset**: The UTC date and time of when your quota will be reset.

{: .code .red}
	curl -I 'http://app.ticketmaster.com/discovery/v1/events.json?keyword=Queen&apikey=xxx'

	HTTP/1.1 200 OK
	Access-Control-Allow-Headers: origin, x-requested-with, accept
	Access-Control-Allow-Methods: GET, PUT, POST, DELETE
	Access-Control-Allow-Origin: *
	Access-Control-Max-Age: 3628800
	Content-Length: 10125
	Content-Type: application/json;charset=UTF-8
	Date: Mon, 18 Jan 2016 05:59:31 GMT
	Rate-Limit: 5000
	Rate-Limit-Available: 4978
	Rate-Limit-Over: 0
	Rate-Limit-Reset: 1453180594367
{'fraction_non_alphanumeric': 0.14728523042184133, 'fraction_numerical': 0.01785897567484348, 'mean_word_length': 2.941747572815534, 'pattern_counts': {'":': 0, '<': 163, '<?xml version=': 0, '>': 163, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 8, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6431757', 'n_tokens_mistral': 3278, 'n_tokens_neox': 2971, 'n_words': 992}