Ticket Evolution API

https://ticketevolution.atlassian.net/wiki/spaces/API/
Admin
Ticket Evolution API provides developers with comprehensive integration tools for ticket processing,...
Tokens:89,321
Snippets:202
Trust Score:10
Update:1 year ago
Show doc for...
Tokens:
Raw
### Ticket Evolution API - How To Articles

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394116

A collection of how-to articles and guides for using the Ticket Evolution API, providing practical instructions and examples for common tasks.

```APIDOC
How To Articles:
  - Link: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/21233763/How%2BTo%2BArticles
```

--------------------------------

### Ticket Evolution API - How To Articles

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394116/Email+Addresses

A collection of how-to articles and guides for using the Ticket Evolution API, providing practical instructions and examples for common tasks.

```APIDOC
How To Articles:
  - Link: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/21233763/How%2BTo%2BArticles
```

--------------------------------

### Ticket Evolution API How-To Guides

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/1524891662/HOW+TO+Process+a+Substitution+via+the+API

A collection of guides detailing specific API functionalities and integration steps for the Ticket Evolution platform. These cover common developer tasks and scenarios.

```APIDOC
HOWTO: Support Integrated MLB Sales
  Description: Guide on how to support integrated MLB sales using the Ticket Evolution API.
  URL: /wiki/spaces/API/pages/3537469463/HOWTO%2BSupport%2BIntegrated%2BMLB%2BSales
```

```APIDOC
HOWTO: Automate TEvo Order Processing
  Description: Instructions for automating order processing within the Ticket Evolution platform via the API.
  URL: /wiki/spaces/API/pages/21233775/HOWTO%2BAutomate%2BTEvo%2BOrder%2BProcessing
```

```APIDOC
HOWTO: Setup a Third Party Automator
  Description: Steps to set up a third-party automation tool to interact with the Ticket Evolution API.
  URL: /wiki/spaces/API/pages/21233796/HOWTO%2BSetup%2Ba%2BThird%2BParty%2BAutomator
```

```APIDOC
HOWTO: Create Orders Using The API
  Description: A guide on the process of creating new orders programmatically through the Ticket Evolution API.
  URL: /wiki/spaces/API/pages/25722884/HOWTO%2BCreate%2BOrders%2BUsing%2BThe%2BAPI
```

```APIDOC
HOWTO: Create A New User For My Office
  Description: Instructions for creating new user accounts for an office environment using the API.
  URL: /wiki/spaces/API/pages/21233792/HOWTO%2BCreate%2BA%2BNew%2BUser%2BFor%2BMy%2BOffice
```

```APIDOC
HOW TO: Integrate the Riskified Fraud Service to your Website
  Description: Guide on integrating the Riskified fraud detection service with your website using the Ticket Evolution API.
  URL: /wiki/spaces/API/pages/819167268/HOW%2BTO%2BIntegrate%2Bthe%2BRiskified%2BFraud%2BService%2Bto%2Byour%2BWebsite
```

```APIDOC
HOW TO: Process a Substitution via the API
  Description: Detailed steps on how to process a ticket substitution using the Ticket Evolution API.
  URL: /wiki/spaces/API/pages/1524891662/HOW%2BTO%2BProcess%2Ba%2BSubstitution%2Bvia%2Bthe%2BAPI
```

```APIDOC
HOW TO: Automate Flash & TM Mobile Transfers
  Description: Guide for automating the transfer of Flash & TM mobile tickets through the API.
  URL: /wiki/spaces/API/pages/676986886/HOW%2BTO%2BAutomate%2BFlash%2BTM%2BMobile%2BTransfers
```

--------------------------------

### Get Listing Details Example

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2895052808

Demonstrates a typical request to retrieve details for a specific listing using its ID and the expected JSON response structure.

```APIDOC
GET /v9/listings/{listing_id}

Retrieves detailed information about a specific ticket listing.

Parameters:
- listing_id (path parameter): The unique identifier for the listing.

Example Request:
GET /v9/listings/1233641554

Example Response:
{
  "automated": false,
  "available_quantity": 7,
  "discounted": false,
  "eticket": false,
  "featured": true,
  "format": "Flash_seats",
  "id": 1272907745,
  "in_hand": false,
  "in_hand_on": "2023-02-26",
  "instant_delivery": false,
  "owned": true,
  "public_notes": "Orders for these tickets will be remain pending. Scan your tickets from your mobile phone for this event. These tickets are for testing purposes only.",
  "quantity": 7,
  "retail_price": 11.74,
  "retail_price_inclusive": 14.08,
  "row": "11",
  "section": "102",
  "service_fee": 0,
  "signature": "NlhRYldEQ3pybWN4QUJhK0xJbE1paEswaiswK0N6MW14a2syWWlvOXlIOD0tLTlESmI2bEdQbkRwd0N2WElWdHFIOFE9PQ==--72913d99d19f25320515dd08abfa80931f0ede3f",
  "splits": [
    1,
    2,
    3,
    4,
    5,
    7
  ],
  "tevo_section_name": "102",
  "type": "event",
  "view_type": null,
  "wheelchair": false,
  "wholesale_price": 11.18,
  "face_value": 15.0,
  "seller_cost": 17.89
}

Related API Documentation:
- [api_docs_listings](/wiki/label/API/api_docs_listings)
```

--------------------------------

### API How-To Guides

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/1524891662

Collection of guides detailing specific API operations and integration steps for the Ticket Evolution platform. These articles cover common tasks and best practices for developers interacting with the API.

```APIDOC
HOWTO: Support Integrated MLB Sales
  - Description: Guide on how to integrate and support MLB sales through the API.
  - Related: Other HOWTO articles for specific integrations.
```

```APIDOC
HOWTO: Automate TEvo Order Processing
  - Description: Instructions for automating the order processing workflow using the Ticket Evolution API.
  - Related: Guides on order creation and management.
```

```APIDOC
HOWTO: Setup a Third Party Automator
  - Description: Steps to configure and set up third-party automation tools with the Ticket Evolution API.
  - Related: API authentication and integration guides.
```

```APIDOC
HOWTO: Create Orders Using The API
  - Description: Detailed guide on the process of creating new orders via API calls.
  - Parameters:
    - Typically involves sending order details, event information, and payment data.
  - Returns:
    - Confirmation of order creation or error messages.
  - Related: Order management and notification guides.
```

```APIDOC
HOWTO: Create A New User For My Office
  - Description: Instructions for programmatically creating new user accounts within an office context via the API.
  - Parameters:
    - User details (name, email, role, etc.).
  - Returns:
    - New user ID or status of creation.
  - Related: User management and authentication.
```

```APIDOC
HOW TO: Integrate the Riskified Fraud Service to your Website
  - Description: Guide for integrating the Riskified fraud detection service with your website using the Ticket Evolution API.
  - Related: Payment processing and security features.
```

```APIDOC
HOW TO: Process a Substitution via the API
  - Description: Steps for handling ticket substitutions programmatically through the API.
  - Parameters:
    - Original ticket details, new ticket details, reason for substitution.
  - Returns:
    - Status of the substitution process.
  - Related: Ticket management and event operations.
```

```APIDOC
HOW TO: Automate Flash & TM Mobile Transfers
  - Description: Guide on automating the transfer of tickets, specifically for Flash and TM Mobile events, using the API.
  - Related: Event-specific integrations and ticket fulfillment.
```

--------------------------------

### Ticket Evolution API Overview and Guides

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2321547302

This section provides an overview of the Ticket Evolution API and links to various guides for specific functionalities. It covers topics such as hosted checkout, credit card integration, order notifications via webhooks, transactional emails, and resources for developers.

```APIDOC
API Documentation Structure:

- Overview: General introduction to the API.
- Hosted Checkout: Information on integrating hosted checkout flows.
- Current Version: Details on the current API version.
- Credit Card Integration: Guides for processing credit card payments.
- Fraud Protection by Riskified: Integration details for fraud protection services.
- Order Notifications (Webhooks): How to receive real-time order updates.
- Transactional Emails: Information on sending transactional emails via the API.
- Resources: Additional developer resources.
- Libraries: Available client libraries for different programming languages.
```

--------------------------------

### Ticket Evolution API - Creating Orders

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/overview

Guides on how to create orders through the Ticket Evolution API. This includes specific instructions for different user roles such as Partners, Brokers, and Affiliates, highlighting variations in the process.

```APIDOC
Creating Orders:
  - General guide: /wiki/spaces/API/pages/357630008/11.2BCreating%2BOrders
  - For Partners and Brokers: /wiki/spaces/API/pages/357204018/11.1%2BCreating%2BOrders%2BPartners%2Band%2BBrokers
  - For Affiliates: /wiki/spaces/API/pages/357630027/11.2%2BCreating%2BOrders%2BAffiliates
```

--------------------------------

### How-To Articles for Ticket Evolution API

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2321547302

A collection of step-by-step guides for performing specific tasks using the Ticket Evolution API. These articles cover common integration scenarios and operational procedures.

```APIDOC
How-To Articles:

- HOWTO: Support Integrated MLB Sales
- HOWTO: Automate TEvo Order Processing
  - Processing Orders via Order Integration
  - Processing Orders via Webhooks
  - Processing Orders via Polling
- HOWTO: Setup a Third Party Automator
- HOWTO: Create Orders Using The API
- HOWTO: Create A New User For My Office
- HOW TO: Integrate the Riskified Fraud Service to your Website
- HOW TO: Process a Substitution via the API
- HOW TO: Automate Flash & TM Mobile Transfers
```

--------------------------------

### Ticket Evolution API Overview and Guides

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2321547302/Processing+Orders+via+Order+Integration

This section provides an overview of the Ticket Evolution API and links to various guides for specific functionalities. It covers topics such as hosted checkout, credit card integration, order notifications via webhooks, transactional emails, and resources for developers.

```APIDOC
API Documentation Structure:

- Overview: General introduction to the API.
- Hosted Checkout: Information on integrating hosted checkout flows.
- Current Version: Details on the current API version.
- Credit Card Integration: Guides for processing credit card payments.
- Fraud Protection by Riskified: Integration details for fraud protection services.
- Order Notifications (Webhooks): How to receive real-time order updates.
- Transactional Emails: Information on sending transactional emails via the API.
- Resources: Additional developer resources.
- Libraries: Available client libraries for different programming languages.
```

--------------------------------

### How-To Articles for Ticket Evolution API

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2321547302/Processing+Orders+via+Order+Integration

A collection of step-by-step guides for performing specific tasks using the Ticket Evolution API. These articles cover common integration scenarios and operational procedures.

```APIDOC
How-To Articles:

- HOWTO: Support Integrated MLB Sales
- HOWTO: Automate TEvo Order Processing
  - Processing Orders via Order Integration
  - Processing Orders via Webhooks
  - Processing Orders via Polling
- HOWTO: Setup a Third Party Automator
- HOWTO: Create Orders Using The API
- HOWTO: Create A New User For My Office
- HOW TO: Integrate the Riskified Fraud Service to your Website
- HOW TO: Process a Substitution via the API
- HOW TO: Automate Flash & TM Mobile Transfers
```

--------------------------------

### Ticket Evolution API - Getting Access

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/overview

Details the process for obtaining access to the Ticket Evolution API, including specific guidance for brokers.

```APIDOC
Getting Access:
  - General Access: /wiki/spaces/API/pages/342229112/01.2BGetting%2BAccess%2Bto%2Bthe%2BTicket%2BEvolution%2BAPI
  - For Brokers: /wiki/spaces/API/pages/342229140/01.1%2BGetting%2BAccess%2Bto%2Bthe%2BTicket%2BEvolution%2BAPI%2BBrokers
```

--------------------------------

### Items Index API Endpoint

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/12550147/Items+Index

Provides details for the GET request to list all items for a specific order. Includes URL, parameters, and an example JSON response.

```APIDOC
Items Index API Endpoint:
  GET /v9/orders/:order_id/items
  Description: List all of the items present on an order.
  Parameters:
    order_id: The ID of the order to retrieve items for.
  Returns: A JSON object containing total entries and a list of items.
  Example Request:
    /v9/orders/75214/items
  Example Response:
    {
      "total_entries": 1,
      "items": [
        {
          "ticket_group": {
            "event": {
              "venue": {
                "address": {
                  "region": "NJ",
                  "locality": "Newark"
                },
                "name": "Prudential Center"
              },
              "occurs_at": "2013-08-06T11:00:00Z",
              "name": "Washington Mystics at New York Liberty",
              "url": "/events/432985",
              "id": "432985"
            },
            "office_name": "Main Office",
            "tickets": [
              {
                "purchase_order_id": null,
                "seat": "13"
              },
              {
                "purchase_order_id": null,
                "seat": "12"
              },
              {
                "purchase_order_id": null,
                "seat": "11"
              },
              {
                "purchase_order_id": null,
                "seat": "10"
              },
              {
                "purchase_order_id": null,
                "seat": "7"
              },
              {
                "purchase_order_id": null,
                "seat": "9"
              },
              {
                "purchase_order_id": null,
                "seat": "8"
              }
            ],
            "remote_id": "109946",
            "brokerage_name": "TicketeStore",
            "wholesale_price": "27.0",
            "format": null,
            "row": "7",
            "external_notes": null,
            "seats": [
              "7",
              "8",
              "9",
              "10",
              "11",
              "12",
              "13"
            ],
            "office_id": "1454",
            "section": "7",
            "retail_price": "27.0",
            "quantity": 7,
            "brokerage_id": "1491",
            "url": "/ticket_groups/1454"
          },
          "eticket_finalized_at": null,
          "updated_at": "2013-08-23T13:54:52Z",
          "created_at": "2013-08-01T18:06:28Z",
          "delivery_id": 28731,
          "eticket_pdf_pages": null,
          "eticket_file_size": null,
          "eticket_downloaded_at": null,
          "order_item_id": 62792,
          "eticket_updated_at": null,
          "cost": "",
          "quantity": 7,
          "has_spec_tickets": false,
          "price": "27.0",
          "eticket_downloaded_by": null,
          "url": "/orders/75214/items/62792",
          "id": 26319,
          "eticket_thumbnails": [],
          "eticket_finalized": null,
          "eticket_delivery": true
        }
      ]
    }
```

--------------------------------

### Ticket Evolution API - Specific Integrations and Features

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/overview

Covers specific integration guides and features, such as integrating the Riskified Fraud Service, processing substitutions via the API, and handling integrated MLB sales.

```APIDOC
Specific Integrations:
  - Integrate Riskified Fraud Service: /wiki/spaces/API/pages/819167268/HOW%2BTO%2BIntegrate%2Bthe%2BRiskified%2BFraud%2BService%2Bto%2Byour%2BWebsite
  - Process a Substitution via API: /wiki/spaces/API/pages/1524891662/HOW%2BTO%2BProcess%2Ba%2BSubstitution%2Bvia%2Bthe%2BAPI
  - Support Integrated MLB Sales: /wiki/spaces/API/pages/3537469463/HOWTO%2BSupport%2BIntegrated%2BMLB%2BSales
```

--------------------------------

### Tax Quotes API

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2900459521/Tax+Quotes

Get a quote for the amount of tax that will be collected on a purchase from Ticket Evolution. This section provides a description of the functionality and an example of an API response.

```APIDOC
# Tax Quotes

Description: Get a quote for the amount of tax that will be collected on a purchase from Ticket Evolution.

Example API Response:
```json
{
  "serverDuration": 13,
  "requestCorrelationId": "9c3b9b745d8e460cb5b9b3cdc123d173"
}
```
```

--------------------------------

### Ticket Evolution API - Resources Overview

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394116/Email+Addresses

General resources and documentation links for the Ticket Evolution API, including an overview and links to libraries.

```APIDOC
Overview:
  - Link: /wiki/spaces/API/pages/983121/Overview

Resources:
  - Link: /wiki/spaces/API/pages/983123/Resources
```

--------------------------------

### Ticket Evolution API - Resources Overview

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394116

General resources and documentation links for the Ticket Evolution API, including an overview and links to libraries.

```APIDOC
Overview:
  - Link: /wiki/spaces/API/pages/983121/Overview

Resources:
  - Link: /wiki/spaces/API/pages/983123/Resources
```

--------------------------------

### Example JSON Response

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/259194898/Shipments+Complete+-+Deprecated

A sample JSON object representing server response metadata.

```json
{
  "serverDuration": 13,
  "requestCorrelationId": "3c3b4ba9f9fc4c5eae697eccdba8f05e"
}
```

--------------------------------

### Get Listing by ID

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2895052808

Retrieves a specific listing by its ID. The response includes details on ticket availability and available purchase quantities.

```APIDOC
GET /listings/{id}
  Description: Returns the specified Listing.
  Parameters:
    id (Integer, Required): ID of the Listing.
  Returns:
    available_quantity (Integer): Indicates how many tickets are currently available to sell.
    splits (Array<Integer>): An array showing which quantities are available to purchase.
  Notes:
    - If testing in the Sandbox, the events named "Test Event" is recommended as it has several large listings of various types and formats.
    - Example for splits: `[1,2,3,4,5,7]` means an attempt to purchase 6 tickets will fail.
```

--------------------------------

### Resources and Libraries

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394119/Clients+Email+Addresses+Index

Information on available resources and client libraries for interacting with the API.

```APIDOC
Resources:
  - (Links or descriptions of API resources)

Libraries:
  - (Information on available SDKs or client libraries for various programming languages)
```

--------------------------------

### GET /v9/clients/:client_id/email_addresses

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394119/Clients+Email+Addresses+Index

Lists email addresses for a specified client. Supports filtering by label, address, creation, and update timestamps. Requires API credentials.

```APIDOC
GET /v9/clients/:client_id/email_addresses
  Description: List Email Addresses for a specified Client
  Credential Type: API
  Supports Pagination: Yes
  Parameters:
    label (String, Optional, Query): Arbitrary description for the email address. Must be an exact match.
    address (String, Optional, Query): Email address. Must be an exact match.
    created_at (Date (ISO_8601), Optional, Query): Creation timestamp. Supports conditionals.
    updated_at (Date (ISO_8601), Optional, Query): Last updated timestamp. Supports conditionals.
  Examples:
    Request: GET /v9/clients/12345/email_addresses
    Response: 
```

--------------------------------

### Ticket Evolution API - Client Management

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/overview

Documentation on managing clients within the Ticket Evolution system via the API. This includes the process for creating new clients and associating credit card information with them.

```APIDOC
Client Management:
  - Creating a Client: /wiki/spaces/API/pages/342393128/09.2BCreating%2Ba%2BClient
  - Creating Credit Cards for a Client: /wiki/spaces/API/pages/357466142/10.2BCreating%2BCredit%2BCards%2Bfor%2Ba%2BClient
```

--------------------------------

### GET /v9/listings Endpoint

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/2853797930

Retrieves all listings for a specified event. This endpoint does not support pagination and returns all listings matching the query. Each listing includes available quantity and split details.

```APIDOC
Endpoint: GET /v9/listings

Description: Lists all listings for an event.

URL: /v9/listings

Credential Type: APICredential|UserCredential

Supports Pagination: No

Long Description: Returns **all** listings for the given **event_id**. *This endpoint does not support pagination—all listings matching your query will be returned.*

Each Listing in the response will include an `available_quantity` property, which indicates how many tickets are currently available to sell.

The `splits` array shows which quantities are available to purchase. For example, in `splits:[1,2,3,4,5,7]` an attempt to purchase 6 tickets will fail.

Parameters:
  - Name: `event_id`
    Description: ID of the Event for which you would like to get listings
    Value Type: Integer
    Required: Yes

  - Name: `type`
    Description: Filter by type to specify what types of tickets you will receive for an event: `event`, `parking`
    Value Type: String
    Required: Optional

  - Name: `quantity`
    Description: Filter by number of tickets greater than or equal to the passed value
    Value Type: Integer
    Required: Optional

  - Name: `section`
    Description: Filter by exact match section
    Value Type: String
    Required: Optional

  - Name: `row`
    Description: Filter by exact match row
    Value Type: String
    Required: Optional

  - Name: `owned`
    Description: Filter by your own listings. Setting this to `true` will return only ticket groups owned by any of the offices belonging to the same Brokerage as the requester.
    Value Type: Boolean
    Required: Optional

  - Name: `order_by`
    Description: Sort results by any of the following parameters: `retail_price`, `section`, `row`, `format`. Adjust the sort direction by appending `ASC` or `DESC.` e.g.: `order_by=retail_price+DESC`
    Value Type: String
    Required: Optional

Response Properties:
  See Listings / Show for an explanation of the properties for each ticket group object.
```

--------------------------------

### API Overview and Resources

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394131/Clients+Phone+Numbers+Index

Provides a high-level overview of the Ticket Evolution API and lists key resources available for integration. This includes sections for Accounts, Clients, Events, Listings, Orders, Payments, Performers, and more.

```APIDOC
API Documentation Structure:

- Overview
- Hosted Checkout
- Current Version

Resources:
  - Accounts
  - Categories
  - Clients
    - Clients / Create
    - Clients / Update
    - Addresses
    - Clients / Delete
    - Clients / Index
    - Clients / Show
    - Email Addresses
    - Phone Numbers
      - Clients / Phone Numbers / Create
      - Clients / Phone Numbers / Delete
      - Clients / Phone Numbers / Index
      - Clients / Phone Numbers / Show
      - Clients / Phone Numbers / Update
    - Clients / Braintree Client Token
  - Companies
  - Credentials
  - Events
  - Imports (Upload Inventory File)
  - Inventory
  - Listings
  - Merchant Accounts
  - Orders
  - Payments
  - Performers
  - Promotion Codes
  - Rate Options
  - Searching / Global
  - Settings
  - Shipments
  - Tax Quotes
  - Ticket Groups
  - Tickets
  - Users
  - Venue Configurations
  - Venues
  - External Listing API

Integrations & Features:
  - Credit Card Integration
  - Fraud Protection by Riskified
  - Order Notifications (Webhooks)
  - Transactional Emails

Supporting Information:
  - How To Articles
  - Resources
  - Libraries
  - Test Api Page can be Deleted
```

--------------------------------

### Ticket Evolution API - Orders and Listings

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/1524891662/HOW+TO+Process+a+Substitution+via+the+API

Documentation for the Ticket Evolution API endpoints related to searching listings and creating orders. This includes parameters for filtering listings and the structure for submitting substitution orders.

```APIDOC
GET /v9/listings
  Description: Searches for ticket groups based on provided query parameters.
  Authentication: Requires X-Signature and X-Token headers.
  Query Parameters:
    - event_id (required): The ID of the event to filter listings.
    - quantity (optional): The desired quantity of tickets, used to check availability and rules.
  Example Usage:
    curl -i -X GET -H "X-Signature: <REQUEST SIGNATURE>" -H "X-Token: <API TOKEN>" --url 'https://api.ticketevolution.com/v9/listings?event_id=9876543&quantity=2'

POST /v9/orders
  Description: Creates a new order, including processing substitutions for rejected orders.
  Authentication: Requires X-Signature and X-Token headers.
  Headers:
    - Content-Type: application/json
  Request Body:
    Type: JSON object
    Structure:
      {
        "orders": [
          {
            "shipped_items": [
              {
                "items": [
                  {
                    "price": "number",
                    "quantity": "integer",
                    "ticket_group_id": "integer"
                  }
                ]
              }
            ],
            "substitute_order_link_id": "integer" 
          }
        ]
      }
    Parameters:
      - orders (array): An array of order objects.
        - shipped_items (array): Details of items being shipped or substituted.
          - items (array): Individual item details.
            - price (number): The wholesale price for the item.
            - quantity (integer): The quantity of the item.
            - ticket_group_id (integer): The ID of the ticket group for this item.
        - substitute_order_link_id (integer): The ID of the original rejected purchase order to link this substitution to.
  Example Request Body:
    {
      "orders": [
        {
          "shipped_items": [
            {
              "items": [
                {
                  "price": 190.1,
                  "quantity": 2,
                  "ticket_group_id": 9876543
                }
              ]
            }
          ],
          "substitute_order_link_id": 228812
        }
      ]
    }
  Example Usage:
    curl -i -X POST -H "X-Signature: <SIGNATURE>" -H "X-Token: <API TOKEN>" -H "Content-Type: application/json" -d '{"orders":[{"shipped_items":[{"items":[{"price":190.1,"quantity":2,"ticket_group_id":9876543}]}],"substitute_order_link_id":228812}]}' --url 'https://api.sandbox.ticketevolution.com/v9/orders?'
```

--------------------------------

### List Client Phone Numbers API

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394131/Clients+Phone+Numbers+Index

Retrieves a list of phone numbers for a specified client. This GET endpoint supports filtering via query parameters and includes pagination capabilities.

```APIDOC
GET /v9/clients/:client_id/phone_numbers

Description: List Phone Numbers for a specified Client

Parameters:
  - client_id (Integer, Required, URI): The ID of the specific Client.
  - country_code (String, Optional, Query): The country calling code.
  - number (String, Optional, Query): The Phone Number.
  - extension (String, Optional, Query): Numbered extension.
  - label (String, Optional, Query): Arbitrary label for describing the number. e.g.: `home`.
  - created_at (Date ISO_8601, Optional, Query, Conditional): Creation timestamp.
  - updated_at (Date ISO_8601, Optional, Query, Conditional): Last updated timestamp.

Supports Pagination: Yes

Example Request:
(No specific request code provided in source)

Example Response:
(No specific response code provided in source)
```

--------------------------------

### Ticket Evolution API - Supporting Resources

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394116/Email+Addresses

Documentation for various supporting resources and functionalities in the Ticket Evolution API. This includes managing credentials, imports, rate options, settings, shipments, and ticket groups.

```APIDOC
Credentials:
  - Details: /wiki/spaces/API/pages/9994364/Credentials

Imports (Upload Inventory File):
  - Details: /wiki/spaces/API/pages/983132/Imports%2BUpload%2BInventory%2BFile

Rate Options:
  - Details: /wiki/spaces/API/pages/34832453/Rate%2BOptions

Settings:
  - Details: /wiki/spaces/API/pages/983183/Settings

Shipments:
  - Details: /wiki/spaces/API/pages/983173/Shipments

Ticket Groups:
  - Details: /wiki/spaces/API/pages/9469956/Ticket%2BGroups
```

--------------------------------

### Ticket Evolution API - Landing Pages and Transfers

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/overview

Details how to leverage the Ticket Evolution API for creating landing pages for events and performers, and how to automate mobile transfers. It also covers integrating with third-party automators.

```APIDOC
Landing Pages & Transfers:
  - Event Landing Pages: /wiki/spaces/API/pages/354910401/08.2BEvent%2BLanding%2BPages
  - Performer Landing Pages: /wiki/spaces/API/pages/342458638/06.2BPerformer%2BLanding%2BPages
  - Venue Landing Pages: /wiki/spaces/API/pages/342229209/07.2BVenue%2BLanding%2BPages
  - Automate Flash & TM Mobile Transfers: /wiki/spaces/API/pages/676986886/HOW%2BTO%2BAutomate%2BFlash%2BTM%2BMobile%2BTransfers
```

--------------------------------

### Items API - Order Item Display

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/11304970/Items

This section details the API functionality for retrieving and displaying information about items associated with an order. It outlines the purpose of the endpoint and provides an example of a typical server response.

```APIDOC
Items API:
  Description: Display information about the items within an order.

  Example Response:
    {
      "serverDuration": 13,
      "requestCorrelationId": "c77de75bec644f3cb978ca19bea631d1"
    }
```

--------------------------------

### Ticket Evolution API - Supporting Resources

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/27394116

Documentation for various supporting resources and functionalities in the Ticket Evolution API. This includes managing credentials, imports, rate options, settings, shipments, and ticket groups.

```APIDOC
Credentials:
  - Details: /wiki/spaces/API/pages/9994364/Credentials

Imports (Upload Inventory File):
  - Details: /wiki/spaces/API/pages/983132/Imports%2BUpload%2BInventory%2BFile

Rate Options:
  - Details: /wiki/spaces/API/pages/34832453/Rate%2BOptions

Settings:
  - Details: /wiki/spaces/API/pages/983183/Settings

Shipments:
  - Details: /wiki/spaces/API/pages/983173/Shipments

Ticket Groups:
  - Details: /wiki/spaces/API/pages/9469956/Ticket%2BGroups
```

--------------------------------

### API Response Example

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/11304970

This snippet demonstrates a typical JSON response structure from an API. It includes server processing duration and a request correlation ID, commonly used for logging and debugging purposes in web services.

```json
{
  "serverDuration": 14,
  "requestCorrelationId": "b9094f742bd94e8aa9bd8c7bf3ec1d6d"
}
```

--------------------------------

### Ticket Evolution API - Client Property Management

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/25722884/HOWTO+Create+Orders+Using+The+API

Covers the creation and management of various client properties, including addresses, phone numbers, and email addresses. Each property has a unique `id` that can be linked to orders. Properties can be created individually or during the order process.

```APIDOC
POST /clients/{client_id}/addresses
  Description: Creates a new address for a client.
  Parameters:
    - client_id (string, required): The ID of the client to associate the address with.
  Requires:
    - address (object, required): Address details including street, city, state, zip, country.
    - label (string, optional, max 20 chars): A label for the address (e.g., 'Home', 'Work').
  Returns: A JSON object containing the newly created address's `id`.

POST /clients/{client_id}/phone_numbers
  Description: Creates a new phone number for a client.
  Parameters:
    - client_id (string, required): The ID of the client.
  Requires:
    - phone_number (string, required): The phone number.
    - label (string, optional, max 20 chars): A label for the phone number (e.g., 'Mobile', 'Work').
  Returns: A JSON object containing the newly created phone number's `id`.

POST /clients/{client_id}/email_addresses
  Description: Creates a new email address for a client.
  Parameters:
    - client_id (string, required): The ID of the client.
  Requires:
    - email_address (string, required): The email address.
    - label (string, optional, max 20 chars): A label for the email address (e.g., 'Personal', 'Work').
  Returns: A JSON object containing the newly created email address's `id`.
```

--------------------------------

### Physical Tickets - FedEx Airbill API

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/21233775/HOWTO+Automate+TEvo+Order+Processing

Handles the process for physical ticket delivery when the shipment type is FedEx. This involves a two-step process: first generating the airbill, and then retrieving it. Specific API endpoints for these actions are referenced but not detailed with code examples in this document.

```APIDOC
POST /v9/orders/{order_id}/shipments/{shipment_id}/generate_airbill

Description:
  Initiates the generation of an airbill for a FedEx shipment associated with an order.
  (Endpoint details and parameters not provided in source text).

Related:
  - Retrieve Airbill API
```

```APIDOC
GET /v9/orders/{order_id}/shipments/{shipment_id}/airbill

Description:
  Retrieves the generated airbill details for a FedEx shipment.
  (Endpoint details and parameters not provided in source text).

Related:
  - Generate Airbill API
```

--------------------------------

### API: GET /v9/tickets/{ticket_group_id} - List Tickets

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/pages/28016763/Tickets+Index

Retrieves a list of tickets from your inventory. This endpoint is used to fetch ticket data based on a specified ticket group ID. Pagination is not supported for this particular API call.

```APIDOC
Endpoint: Tickets / Index

Description: List tickets
Type: GET
URL: /v9/tickets/{ticket_group_id}
Credential Type: API
Supports Pagination: No

Long Description: List tickets from your inventory.

Parameters:
  ticket_group_id: The identifier for the ticket group to list tickets from.
```

--------------------------------

### Ticket Evolution API - Core Concepts and Search

Source: https://ticketevolution.atlassian.net/wiki/spaces/API/overview

Provides foundational information for using the Ticket Evolution API, including basic terminology and how to perform comprehensive searches for events and other data. It also covers displaying events relevant to user locations.

```APIDOC
Core Concepts:
  - Basic Terminology: /wiki/spaces/API/pages/342393010/02.2BBasic%2BTerminology
  - Getting Technical: /wiki/spaces/API/pages/342393034/03.2BGetting%2BTechnical
  - Comprehensive Search: /wiki/spaces/API/pages/342393069/04.2BComprehensive%2BSearch
  - Displaying Events Near Your Users: /wiki/spaces/API/pages/342196567/05.2BDisplaying%2BEvents%2BNear%2BYour%2BUsers
```
Tokens:
Raw