Ticket Tailor MCP

Creates a new bundle in event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Delete a bundle. This action is irreversible. The bundle will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing bundle in event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a check-in or check-out record for an issued ticket. Check-ins track when attendees arrive at or leave an event. This is essential for event management, attendance tracking, and security. You can check in attendees at the door, track early departures, or manage re-entry. The system prevents duplicate check-ins unless explicitly allowed. These records stack up, so the current check-in state of an issued ticket is the sum of its corresponding records. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of check-ins. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a checkout form element by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of checkout form elements. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing checkout form element. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of checkout forms. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a discount by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a discount code that customers can use during checkout to receive reduced pricing. Discount codes are powerful marketing tools that can increase sales, reward loyal customers, or fill seats. You can create percentage-based or fixed-amount discounts, set usage limits, and restrict them to specific ticket types or products. The discount code will be immediately available for customers to use. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Delete a discount. This action is irreversible. The discount will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of discounts. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing discount. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns an event by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

<usecases> Create multiple events with single tool call. Create one or more event series. Create one or more event occurrences for one or more new event series. Create one or more event occurrences for one or more existing event series. Create one or more ticket types for one or more new event series. Create one or more ticket types for one or more existing event series. Create one or more ticket groups for one or more new event series. Create one or more ticket groups for one or more existing event series. </usecases> <instructions> Pass event series related data in eventSeries array to create event series. Pass event occurrences related data in eventOccurrences array to create event occurrences. Pass ticket types related data in ticketTypes array to create ticket types. Pass ticket groups related data in ticketGroups array to create ticket groups. When creating multiple event series with multiple event occurrences and/or multiple ticket types and or multiple ticket groups, use a placeholder for event_series_id in eventOccurrences and ticketTypes and ticketGroups arrays. Placeholder must have a structure of es_placeholder1, es_placeholder2, etc. where the number is the index of the previously created event series. When creating ticket groups and referencing a ticket type that is to be created in the same call, use a placeholder for ticket_type_ids in ticketGroups array. Placeholder must have a structure of tt_placeholder1, tt_placeholder2, etc. where the number is the index of the previously created ticket type. When creating event occurrences or ticket types or ticket groups for an existing event series, use the id of the event series in the event_series_id field. Try to find existing event series first before creating a new one (by name or venue), unless user is explicitly asking to create a new event series. Do not use this tool to update or delete event series, event occurrences or ticket types or ticket groups. Use separate tools for that. </instructions> <validations> Event occurrence end datetime must be after start datetime. Ticket group can not contain bundle_ids when ticket group has max_quantity, max_per_order or min_per_order populated. </validations> Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns an event occurrence by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Delete event occurrence, only if there are no associated orders. Otherwise, set it as hidden. This action is irreversible. The event occurrence will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of event occurrences. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing event occurrence. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns an event series by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Delete an event series and its associated events. This action is irreversible. The event series and its events will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Retrieves a paginated list of event series from your Ticket Tailor account. Event series are collections of related events (like a recurring concert series or festival). Use this to browse, search, and filter your event series by status, name, venue, or creation date. This is a read-only operation that returns metadata about your event series without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Changes the status of an event series (publish, draft, or close sales). Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Retrieves a paginated list of individual event occurrences from your Ticket Tailor account. Events are specific instances within an event series (typically either for time slot admission; or else individual instances of multi-day events like 'Saturday' or 'Sunday' festival tickets, or 'Workshop Session A'). Use this to browse, search, and filter your events by status, name, venue, or date range. This is a read-only operation that returns metadata about your events without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a hold by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a new hold. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Delete a hold. This action is irreversible. The hold will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of holds. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing hold. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns an issued membership by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a new issued membership for a membership type. An issued membership represents an actual membership given to a person. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a redemption for an issued membership at a specific event. This records that the issued membership was used for entry to the event. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a paginated list of issued memberships. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing issued membership. Only fixed date types are allowed when updating. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Voids an existing issued membership. A voided membership cannot be used for redemptions. This action is irreversible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns an issued ticket by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a new issued ticket for an event occurrence from available inventory. Issued tickets represent actual tickets that have been allocated to a specific person and can be used for entry. This tool can create tickets from either existing ticket type inventory or from a hold (reserved tickets). The created ticket will be immediately available for check-in and will be included in ticket counts. Ticket Tailor fees apply to issued tickets created via the Ticket Tailor API, irrespective of whether those tickets are free or paid-for. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of issued tickets. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Voids an issued ticket. This action is irreversible. This will only mark the ticket as voided (no longer valid) and will not cancel an entire order or issue a refund. You can also void an issued ticket to a hold, which will create a hold from the issued ticket and not put the allocation back on sale. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a temporary signed URL for the issued membership photo. The URL has an expiry time after which it will no longer be accessible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a membership type by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a new membership type. Membership types define the configuration for issued memberships including validity periods, redemption limits, and whether photos are required. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Deletes a membership type. A membership type can only be deleted if it has no issued memberships and no linked products. This action is irreversible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a paginated list of membership types. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing membership type. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns an order by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Confirm an offline payment has been paid for an order. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Retrieves a paginated list of customer orders from your Ticket Tailor account. Orders represent completed ticket (and/or product) purchases and contain information about the buyer, items purchased, payment status, and order details. Use this to track sales, analyze customer data, and manage order fulfillment. This is a read-only operation that returns order information without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Updates an existing order. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a new override for event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of overrides. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Update existing override. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Retrieve a comprehensive overview of your Ticket Tailor box office account, including key metrics, account information, and summary statistics. This provides a high-level dashboard view with data about your events, sales, and account status. Useful for getting a quick snapshot of your business performance and account health. This is a read-only operation that returns account summary information without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Tests connectivity to the Ticket Tailor API server and retrieves version information. This is a lightweight health check that verifies your API credentials are valid and the service is responding. Useful for troubleshooting connection issues, validating API access, or checking service status. Returns server version details and confirms your authentication is working properly. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a product by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Creates a new product that can be sold alongside tickets. Products are additional items like merchandise, parking passes, meal vouchers, or special add-ons that customers can purchase during the ticket buying process. Products can be linked to specific event series or made available across all events, or sold via a standalone store (not yet available through the API). They can have their own pricing, inventory limits, and delivery instructions. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Delete a product. This action is irreversible. The product will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.

Returns a list of products. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API.