Skip to main content
Ticket Tailor MCP logo
  • Category: model context protocol
  • Auth: DCR_OAUTH
  • Composio-managed OAuth available? No
  • Tools: 77
  • Triggers: 0
  • Slug: TICKET_TAILOR_MCP
  • Version: 20261018_00

Tools

Slug: TICKET_TAILOR_MCP_BUNDLE_CREATECreates 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.

Input Parameters

string
required
Name of the bundle
integer
required
Price of the bundle in cents
string ("ADMIN_ONLY" | "HIDDEN" | "LOCKED" | "SOLD_OUT" | "ON_SALE" | "UNAVAILABLE")
Bundle status
string
Code to access a protected bundle
integer
Booking fee which is charged per bundle to the customer and the funds are paid to you. We would recommend charging no more than 10% of the bundle price.
string
required
Description of the bundle
array
List of product IDs included in the bundle. Product id must have the prefix ‘pr_’
array
required
List of ticket type IDs included in the bundle. Ticket type id must have the prefix ‘tt_’
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_BUNDLE_DELETEDelete 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.

Input Parameters

string
required
The unique identifier for the bundle to delete. Must have the prefix ‘bu_’
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_BUNDLE_UPDATEUpdates 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.

Input Parameters

string
Name of the bundle
integer
Price of the bundle in cents
string ("ADMIN_ONLY" | "HIDDEN" | "LOCKED" | "SOLD_OUT" | "ON_SALE" | "UNAVAILABLE")
Bundle status
string
required
The unique identifier for the bundle to update. Must have the prefix ‘bu_’
string
Code to access a protected bundle
integer
Booking fee which is charged per bundle to the customer and the funds are paid to you. We would recommend charging no more than 10% of the bundle price.
string
Description of the bundle
array
List of product IDs included in the bundle. Product id must have the prefix ‘pr_’
array
List of ticket type IDs included in the bundle. Ticket type id must have the prefix ‘tt_’
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_CHECK_IN_CREATECreates 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.

Input Parameters

number
required
The check-in action: 1 for check-in (attendee arriving), -1 for check-out (attendee leaving). Use 1 to mark attendance, -1 to record early departure or re-entry
integer
Unix timestamp (in seconds) when the check-in occurred. If not provided, the current time will be used. Useful for backdating check-ins or bulk imports
string
A unique identifier to prevent duplicate check-ins when retrying failed operations. If not provided, Ticket Tailor will generate one automatically. Essential for reliable check-in systems
string
required
The unique identifier of the issued ticket to check in or check out. This is the ticket that will be marked as attended or left. Must have the prefix ‘it_’
Slug: TICKET_TAILOR_MCP_CHECK_INS_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string
The event ID of the check-in. Must have the prefix ‘ev_’
number
Unix timestamp for created at date
number
Unix timestamp that returns items with matched check_in_at value.
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
The event series ID of the check-in. Must have the prefix ‘es_’
number
Unix timestamp that returns items with check_in_at greater than the value.
number
Unix timestamp that returns items with check_in_at less than the value.
string
The issued ticket ID of the check-in. Must have the prefix ‘it_’
number
Unix timestamp that returns items with check_in_at greater than or equal to the value.
number
Unix timestamp that returns items with check_in_at less than or equal to the value.
Slug: TICKET_TAILOR_MCP_CHECKOUT_FORM_ELEMENT_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the checkout form. Must have the prefix ‘cf_’
string
required
The unique identifier for the checkout form element. Must have the prefix ‘cfe_’
Slug: TICKET_TAILOR_MCP_CHECKOUT_FORM_ELEMENTS_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string
The ID of the first item in the next page.
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
required
The unique identifier for the checkout form. Must have the prefix ‘cf_’
Slug: TICKET_TAILOR_MCP_CHECKOUT_FORM_ELEMENT_UPDATEUpdates 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.

Input Parameters

string ("multiCheckbox" | "radio" | "select")
The type of the checkout form element
array
The list of answers for the checkout form element
string
The question for the checkout form element
boolean
Whether the checkout form element is required to answer
boolean
Whether the checkout form element is asked globally or per ticket
string
required
The unique identifier for the checkout form. Must have the prefix ‘cf_’
string
required
The unique identifier for the checkout form element. Must have the prefix ‘cfe_’
Slug: TICKET_TAILOR_MCP_CHECKOUT_FORMS_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string
The ID of the first item in the next page.
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_DISCOUNT_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the discount. Must have the prefix ‘di_’
Slug: TICKET_TAILOR_MCP_DISCOUNT_CREATECreates 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.

Input Parameters

string
required
The actual discount code that customers will enter at checkout (e.g., ‘EARLYBIRD’, ‘STUDENT20’, ‘HOLIDAY50’). Should be memorable and easy to type and preferably unique
string
required
A descriptive name for the discount code (e.g., ‘Early Bird Discount’, ‘Student Discount’, ‘Holiday Special’). This is for internal reference and appears in your admin dashboard
string ("fixed_amount" | "percentage")
required
The type of discount: ‘fixed_amount’ reduces the item price by a specific amount, ‘percentage’ reduces the price by a percentage of the original cost
integer
For fixed_amount discounts, the amount to subtract from the item price in cents (e.g., 1000 = $10.00 off). Required when type is ‘fixed_amount’
integer
Unix timestamp (in seconds) when the discount code expires. After this date, the code will no longer be valid. Leave empty for no expiration
array
Array of product IDs where this discount can be applied. If empty, the discount applies to all products. Product id must have the prefix ‘pr_’
integer
Fixed amount to reduce the booking fee by, in cents (e.g., 500 = $5.00 off booking fee). Can be used with either discount type
integer
Maximum number of tickets in a single order that can use this discount code. Prevents abuse of bulk discounts
integer
Minimum number of tickets that must be purchased in a single order to use this discount code. Useful for encouraging larger purchases
array
Array of ticket type IDs where this discount can be applied. If empty, the discount applies to all ticket types. Ticket type id must have the prefix ‘tt_’
integer
For percentage discounts, the percentage to reduce the item price by (e.g., 20 = 20% off). Required when type is ‘percentage’
integer
Maximum number of times this discount code can be used across all customers. Once reached, the code becomes invalid. Leave empty for unlimited usage
integer
Percentage to reduce the booking fee by (e.g., 50 = 50% off booking fee). Can be used with either discount type
Slug: TICKET_TAILOR_MCP_DISCOUNT_DELETEDelete 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.

Input Parameters

string
required
The unique identifier for the existing discount to delete. Must have the prefix ‘di_’
Slug: TICKET_TAILOR_MCP_DISCOUNTS_GETReturns 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.

Input Parameters

string
The code of the discount
number
The maximum number of items to return.
string
The ID of the first item in the next page.
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_DISCOUNT_UPDATEUpdates 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.

Input Parameters

string
Discount code
string
A descriptive name given to the discount
string ("fixed_amount" | "percentage")
Type of discount. Either a fixed amount or a percentage
integer
Price in cents
integer
Discount code’s expiry date as Unix timestamp
array
An array of associated products with association values (‘1’ = add, ‘0’ = remove, ” = do nothing)
integer
Booking fee amount in cents
string
required
The unique identifier for the existing discount. Must have the prefix ‘di_’
array
An array of associated ticket types with association values (‘1’ = add, ‘0’ = remove, ” = do nothing)
integer
Percent of the price
integer
The maximum number of times this discount can be used
integer
Percent of the booking fee
Slug: TICKET_TAILOR_MCP_EVENT_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the event. Must have the prefix ‘ev_’
Slug: TICKET_TAILOR_MCP_EVENT_MANAGEMENT<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.

Input Parameters

array
required
array
required
array
required
array
required
Slug: TICKET_TAILOR_MCP_EVENT_OCCURRENCE_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the event series. Must have the prefix ‘es_’
string
required
The unique identifier for the event occurrence. Must have the prefix ‘ev_’
Slug: TICKET_TAILOR_MCP_EVENT_OCCURRENCE_DELETEDelete 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.

Input Parameters

string
required
The unique identifier for the existing event series. Must have the prefix ‘es_’
string
required
The unique identifier for the existing event occurrence to delete. Must have the prefix ‘ev_’
Slug: TICKET_TAILOR_MCP_EVENT_OCCURRENCES_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
number
Unix timestamp for end at date
number
Unix timestamp for start at date
number
Unix timestamp for end at date greater than
number
Unix timestamp for end at date less than
number
Unix timestamp for end at date greater than or equal to
number
Unix timestamp for end at date less than or equal to
string
The unique identifier for the override. Must have the prefix ‘ov_’
number
Unix timestamp for start at date greater than
number
Unix timestamp for start at date less than
number
Unix timestamp for start at date greater than or equal to
number
Unix timestamp for start at date less than or equal to
string
The ID of the first item in the next page.
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_EVENT_OCCURRENCE_UPDATEUpdates 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.

Input Parameters

boolean
True, if the event is set to hidden. False otherwise
string
Event end date in the YYYY-MM-dd format
string
Event end time in the HH:ii:ss format
string
Event start date in the YYYY-MM-dd format
string
Event start time in the HH:ii:ss format
URL of the online event
string
The ID of the override that needs to be applied against the event occurrence. Must have the prefix ‘ov_’
boolean
True, if the event is set to unavailable. False otherwise
string
required
The unique identifier for the existing event series. Must have the prefix ‘es_’
string
Optional custom status message when the event is set to unavailable
string
required
The unique identifier for the existing event occurrence. Must have the prefix ‘ev_’
Slug: TICKET_TAILOR_MCP_EVENT_SERIES_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_EVENT_SERIES_DELETEDelete 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.

Input Parameters

string
required
The unique identifier for the event series to delete. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_EVENT_SERIES_GETRetrieves 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.

Input Parameters

string
Search for event series by name. Performs a partial text match on the series name
number
The maximum number of items to return.
string
Filter event series by venue name. Performs a partial text match on the venue field
string ("draft" | "published" | "sales_closed")
Filter event series by their publication status. ‘draft’ shows unpublished series, ‘published’ shows live series accepting orders, ‘sales_closed’ shows series that are no longer selling tickets
number
Unix timestamp for created at date
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_EVENT_SERIES_STATUS_CHANGEChanges 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.

Input Parameters

string ("DRAFT" | "PUBLISHED" | "CLOSE_SALES")
required
New event series status - DRAFT: unpublished, PUBLISHED: live and available, CLOSE_SALES: published but sales closed
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_EVENT_SERIES_UPDATEUpdates 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.

Input Parameters

string
Name of the event series
string
Name of the venue
string
Country of the venue in ISO 3166 format
string ("gbp" | "usd" | "eur" | "sgd" | "aud" | "brl" | "cad" | "czk" | "dkk" | "hkd" | "huf" | "ils" | "jpy" | "myr" | "mxn" | "nok" | "nzd" | "php" | "pln" | "rub" | "sek" | "chf" | "twd" | "thb" | "try")
Information about the currency the event series is configured to use
string
Code to access a protected event series
string
Description of the event series
string
Postal code of the venue
array
An array of associated voucher ids with association values (‘1’ = add, ‘0’ = remove, ” = do nothing)
string
Call to action text used on the event series page
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
string
Specify the name of the online platform used when the event is held online-only. This enables each event occurrence to include a link to the online event.
string ("true" | "no_tickets_available" | "false")
Indicates whether waitlist is enabled for the event series
integer
Timestamp in UTC in seconds when tickets become available for purchase
integer
Timestamp in UTC in seconds when tickets become unavailable for purchase
string
The text displayed on event action buttons and as a title above the waitlist format
string
Description above ticket waitlist form
string
Message to show when tickets are not yet available to purchase. {countdown} is replaced with time remaining until tickets become available
string
Text shown to the user after they have signed up to the waitlist
string
Message to show when tickets are unavailable to purchase
integer
Maximum quantity of tickets that can be sold across all ticket types
Slug: TICKET_TAILOR_MCP_EVENTS_GETRetrieves 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.

Input Parameters

string
Search for events by name. Performs a partial text match on the event name
number
The maximum number of items to return.
string
Filter events by venue name. Performs a partial text match on the venue field
number
Unix timestamp for end at date
string ("draft" | "published" | "sales_closed")
Filter events by their publication status. ‘draft’ shows unpublished events, ‘published’ shows live events accepting orders, ‘sales_closed’ shows events that are no longer selling tickets
number
Unix timestamp for start at date
number
Unix timestamp for end at date greater than
number
Unix timestamp for end at date less than
number
Unix timestamp for end at date greater than or equal to
number
Unix timestamp for end at date less than or equal to
number
Unix timestamp for start at date greater than
number
Unix timestamp for start at date less than
number
Unix timestamp for start at date greater than or equal to
number
Unix timestamp for start at date less than or equal to
string
The ID of the first item in the next page.
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_HOLD_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the hold. Must have the prefix ‘ho_’
Slug: TICKET_TAILOR_MCP_HOLD_CREATECreates 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.

Input Parameters

string
required
A string that gives more information about the created hold
string
required
The ID of the associated event for which to create the hold. Must have the prefix ‘ev_’
array
required
List of ticket types and their quantities
Slug: TICKET_TAILOR_MCP_HOLD_DELETEDelete 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.

Input Parameters

string
required
The unique identifier for the hold to delete. Must have the prefix ‘ho_’
Slug: TICKET_TAILOR_MCP_HOLDS_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string
The unique identifier for the event. Must have the prefix ‘ev_’
number
Unix timestamp for created at date
number
Unix timestamp for updated at date
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for updated at date greater than
number
Unix timestamp for updated at date less than
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
number
Unix timestamp for updated at date greater than or equal to
number
Unix timestamp for updated at date less than or equal to
Slug: TICKET_TAILOR_MCP_HOLD_UPDATEUpdates 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.

Input Parameters

string
A string that gives more information about the created hold
string
required
The unique identifier for the hold. Must have the prefix ‘ho_’
array
An array of associated ticket type IDs with association values (0 = remove, any other integer = keep or add)
Slug: TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the issued membership. Must have the prefix ‘im_’
Slug: TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_CREATECreates 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.

Input Parameters

string
required
Email address of the member
string
required
Last name of the member
string
required
First name of the member
integer
Unix timestamp (UTC) for when the membership expires. Required if valid_to_type is ‘fixed’. When not provided, the membership type’s default is used
string ("fixed" | "relative")
Type of valid to date. ‘fixed’ uses valid_to_date, ‘relative’ uses valid_to_interval_days from issue date. When not provided, the membership type’s default is used
string
Maximum number of times the issued membership can be redeemed. If not provided, the membership type’s default is used. Provide empty string to set unlimited redemptions
integer
Unix timestamp (UTC) for when the issued membership becomes valid. Required if valid_from_type is ‘fixed’. When not provided, the membership type’s default is used
string ("fixed" | "relative")
Type of valid from date. ‘fixed’ uses valid_from_date, ‘relative’ uses the date of issue. When not provided, the membership type’s default is used
string
required
The ID of the membership type. Must have the prefix ‘mt_’
integer
Number of days the membership is valid for from the issue date. Used when valid_to_type is ‘relative’. Must be between 1 and 365. When not provided, the membership type’s default is used
Slug: TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_REDEMPTION_CREATECreates 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.

Input Parameters

string
required
The issued membership code to redeem (e.g., ‘MMABC123’)
string
required
The unique identifier for the event. Must have the prefix ‘ev_’
Slug: TICKET_TAILOR_MCP_ISSUED_MEMBERSHIPS_GETReturns 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.

Input Parameters

string
Filter by email (contains)
number
The maximum number of items to return.
string ("asc" | "desc")
Sort direction when order_by is specified. Defaults to ‘asc’
Search by first name, last name or email (contains)
string ("first_name" | "last_name")
Order results by member’s first_name or last_name
string
Filter by last name (contains)
number
Unix timestamp for created at date
string
Filter by first name (contains)
number
Unix timestamp for updated at date
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for updated at date greater than
number
Unix timestamp for updated at date less than
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
number
Unix timestamp for updated at date greater than or equal to
number
Unix timestamp for updated at date less than or equal to
string ("valid" | "invalid" | "both")
Filter by membership validity status. ‘valid’ returns only currently valid memberships, ‘invalid’ returns expired or voided memberships, ‘both’ returns all. Defaults to ‘valid’
string
Filter by exact membership code
Slug: TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_UPDATEUpdates 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.

Input Parameters

string
Email address of the member
string
Last name of the member
string
First name of the member
integer
Unix timestamp (UTC) for when the issued membership expires
string
Maximum number of times the issued membership can be redeemed. Provide empty string to set unlimited redemptions
integer
Unix timestamp (UTC) for when the issued membership becomes valid
string
required
The unique identifier for the issued membership. Must have the prefix ‘im_’
Slug: TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_VOIDVoids 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.

Input Parameters

string
required
The unique identifier for the issued membership to void. Must have the prefix ‘im_’
Slug: TICKET_TAILOR_MCP_ISSUED_TICKET_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the issued ticket. Must have the prefix ‘it_’
Slug: TICKET_TAILOR_MCP_ISSUED_TICKET_CREATECreates 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.

Input Parameters

string
The email address of the ticket holder. If provided and send_email is true, Ticket Tailor will attempt to automatically send the ticket and event information to this email. The following conditions must be met for the email to be dispatched: (1) a valid email must be provided in the request payload; (2) the box office must be configured to use separate event confirmation emails and order confirmation emails; (3) the event series to which the event belongs must be approved by Ticket Tailor staff.
string
A custom barcode for the ticket. If not provided, Ticket Tailor will generate a unique barcode automatically. Useful for integrating with external systems. This barcode is rendered as a QR code and 1D barcode on the ticket.
string
The unique identifier of a hold (reserved tickets). Required when creating tickets from a hold. The ticket will be created from the reserved inventory in this hold. Hold id must have the prefix ‘ho_’
string
The unique identifier of the specific event occurrence. Required when creating tickets from ticket type inventory. Use this to specify which event the ticket is for. Must have the prefix ‘ev_’
string
required
The full name of the person who will attend the event. This name appears on the ticket and is used for check-in verification. Should match the attendee’s identification
string
An external reference number or identifier for this ticket. Useful for linking tickets to orders in external systems or for internal tracking purposes
boolean
When set to true, Ticket Tailor will attempt to automatically send an email to the attendee containing their ticket and event details. The following conditions must be met for the email to be dispatched: (1) a valid email must be provided in the request payload; (2) the box office must be configured to use separate event confirmation emails and order confirmation emails; (3) the event series to which the event belongs must be approved by Ticket Tailor staff.
string
The unique identifier of the ticket type to create the ticket from. Required when creating from ticket type inventory. Determines the ticket category and pricing. Ticket type id must have the prefix ‘tt_’
Slug: TICKET_TAILOR_MCP_ISSUED_TICKETS_GETReturns 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.

Input Parameters

string
The name of the person attending an event
string
The email of the person attending an event
number
The maximum number of items to return.
string ("valid" | "voided")
The status of the issued ticket
string
The barcode of the issued ticket
string
The unique identifier for the event. Must have the prefix ‘ev_’
string
The unique identifier for the order. Must have the prefix ‘or_’
number
Unix timestamp for created at date
string
The imported reference of the ticket
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_ISSUED_TICKET_VOIDVoids 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.

Input Parameters

boolean
Indicate whether to turn the existing issued ticket into a hold
string
required
The unique identifier for the issued ticket. Must have the prefix ‘it_’
Slug: TICKET_TAILOR_MCP_MEMBERSHIP_PHOTO_SHARE_GETReturns 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.

Input Parameters

string
required
The unique code of the issued membership
Slug: TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the membership type. Must have the prefix ‘mt_’
Slug: TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_CREATECreates 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.

Input Parameters

string
required
Name of the membership type (e.g., ‘Annual Pass’, ‘Monthly Subscription’)
integer
Unix timestamp (UTC) for when memberships of this type expire. Required if valid_to_type is ‘fixed’
string ("fixed" | "relative")
required
Type of valid to date. ‘fixed’ uses valid_to_date, ‘relative’ uses valid_to_interval_days from issue date
string ("true" | "false")
Whether a photo is required when issuing memberships of this type
string
Maximum number of times memberships of this type can be redeemed. If not provided, redemptions are unlimited
integer
Unix timestamp (UTC) for when memberships of this type become valid. Required if valid_from_type is ‘fixed’
string ("fixed" | "relative")
required
Type of valid from date. ‘fixed’ uses valid_from_date for all issued memberships, ‘relative’ uses the date of issue
integer
Number of days the membership is valid for from the issue date. Required if valid_to_type is ‘relative’. Must be between 1 and 365
array
Array of conditions and benefits for this membership type (e.g., [‘Free entry to all events’, ‘10% discount on merchandise’])
Slug: TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_DELETEDeletes 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.

Input Parameters

string
required
The unique identifier for the membership type to delete. Must have the prefix ‘mt_’
Slug: TICKET_TAILOR_MCP_MEMBERSHIP_TYPES_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string
The ID of the first item in the next page.
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_UPDATEUpdates 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.

Input Parameters

string
Name of the membership type
integer
Unix timestamp (UTC) for when memberships of this type expire. Required if valid_to_type is ‘fixed’
string ("fixed" | "relative")
Type of valid to date. ‘fixed’ uses valid_to_date, ‘relative’ uses valid_to_interval_days from issue date
string ("true" | "false")
Whether a photo is required when issuing memberships of this type
string
Maximum number of times memberships of this type can be redeemed. Provide empty string to set unlimited redemptions
integer
Unix timestamp (UTC) for when memberships of this type become valid. Required if valid_from_type is ‘fixed’
string ("fixed" | "relative")
Type of valid from date. ‘fixed’ uses valid_from_date for all issued memberships, ‘relative’ uses the date of issue
string
required
The unique identifier for the membership type. Must have the prefix ‘mt_’
integer
Number of days the membership is valid for from the issue date. Required if valid_to_type is ‘relative’. Must be between 1 and 365
array
Array of conditions and benefits for this membership type
Slug: TICKET_TAILOR_MCP_ORDER_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the order. Must have the prefix ‘or_’
Slug: TICKET_TAILOR_MCP_ORDER_CONFIRM_PAYMENTConfirm 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.

Input Parameters

string
required
The unique identifier for the order. Must have the prefix ‘or_’
string
The transaction ID of the payment
Slug: TICKET_TAILOR_MCP_ORDERS_GETRetrieves 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.

Input Parameters

string
Search for orders by the buyer’s full name. Performs a partial text match on the customer name field
string
Search for orders by the buyer’s email address. Useful for finding all orders from a specific customer, or identifying repeat purchasers.
number
The maximum number of items to return.
string
Filter orders by their current status (e.g., ‘paid’, ‘pending’ if the order is complete but payment has not been received, ‘cancelled’, ‘refunded’).
string
Search for a specific order by its transaction ID. Transaction IDs are unique identifiers for payment processing. These are added automatically to associate the respective transaction if made through Stripe, PayPal, or Square; otherwise they are entered manually.
string
Search for orders containing a specific ticket barcode. Useful for finding orders associated with a particular ticket
string
Filter orders by a specific event occurrence. Returns only orders for tickets to this particular event. Must have the prefix ‘ev_’
string
Filter orders by a specific store. Must have the prefix ‘st_’
number
Unix timestamp for created at date
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
Filter orders by a specific event series. Returns all orders for tickets to any event within this series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_ORDER_UPDATEUpdates 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.

Input Parameters

string
Buyer email address
string
Buyer phone number
string
required
The unique identifier for the order. Must have the prefix ‘or_’
string
The first line of the address
string
The second line of the address
string
The third line of the address
string
Buyer last name
string
Buyer first name
string
Postal code, zip code or postcode
Slug: TICKET_TAILOR_MCP_OVERRIDE_CREATECreates 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.

Input Parameters

string
required
Name of the override
array
required
An array of associated ticket types (prefix id with ‘tt_’), ticket groups (prefix id with ‘tg_’) or bundles (prefix id with ‘bu_’).
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
integer
Maximum number of sellable tickets
Slug: TICKET_TAILOR_MCP_OVERRIDES_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string ("on_sale" | "sold_out" | "unavailable" | "hidden" | "admin_only" | "locked")
A string representing override status
number
Unix timestamp for created at date
string
A string representing the referenced ticket typ or ticket group
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string ("ticket_type" | "ticket_group" | "bundle")
A string representing the reference type, either ticket or ticket_group or bundle
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_OVERRIDE_UPDATEUpdate 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.

Input Parameters

string
Override name
string
required
The unique identifier for the override. Must have the prefix ‘ov_’
array
required
An array of associated ticket types (prefix id with ‘tt_’), ticket groups (prefix id with ‘tg_’) or bundles (prefix id with ‘bu_’).
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
number
Maximum number of sellable tickets
Slug: TICKET_TAILOR_MCP_OVERVIEW_GETRetrieve 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.
Slug: TICKET_TAILOR_MCP_PING_GETTests 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.
Slug: TICKET_TAILOR_MCP_PRODUCT_BY_ID_GETReturns 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.

Input Parameters

string
required
The unique identifier for the product. Must have the prefix ‘pr_’
Slug: TICKET_TAILOR_MCP_PRODUCT_CREATECreates 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.

Input Parameters

string
required
The name of the product that customers will see (e.g., ‘Event T-Shirt’, ‘Parking Pass’, ‘VIP Dinner Package’, ‘Program Book’). Should be clear and descriptive
integer
required
The price of the product in cents (e.g., 1500 = $15.00). This is the base price before any booking fees are applied
string ("ON_SALE" | "SOLD_OUT" | "HIDDEN")
Current status of the product. ‘ON_SALE’ = available for purchase, ‘SOLD_OUT’ = no inventory, ‘HIDDEN’ = not visible to customers
string
The currency for this product’s pricing. If not specified, defaults to your box office currency. Useful for international events with multiple currencies
integer
Total quantity of this product available for sale across all events. Once sold out, no more can be purchased. Leave empty for unlimited inventory
string
The ID of a voucher of type gift card to associate with the product. Must start with ‘vo_’ prefix. Mutually exclusive with issue_ticket_voucher and membership_type_id.
integer
Additional fee charged per product, in cents (e.g., 200 = $2.00). This fee is paid to you and helps cover processing costs. Recommended to keep under 10% of product price
string
Detailed description of the product including features, specifications, or what’s included. Helps customers understand what they’re purchasing
string
Instructions for customers on how to collect or use the product (e.g., ‘Collect at venue entrance’, ‘Email will be sent with download link’, ‘Present voucher at restaurant’)
array
Array of event series IDs where this product will be available for purchase. If empty and linked_to_all_event_series is false, product won’t be available anywhere unless you have set the product to be sold via a standalone store (not yet available through the API). Event series id must have the prefix ‘es_’
string
The ID of a membership type to associate with the product. Must start with ‘mt_’ prefix. Mutually exclusive with issue_ticket_voucher and voucher_id.
integer
Maximum quantity of this product that can be purchased per individual event. Useful for limiting per-event availability
boolean
When true, a QR code voucher will be generated for this product that customers can present for redemption. Useful for digital products or items requiring verification. Mutually exclusive with voucher_id and membership_type_id.
boolean
When true, this product will be available for purchase at all event series. Overrides event_series_ids restrictions
Slug: TICKET_TAILOR_MCP_PRODUCT_DELETEDelete 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.

Input Parameters

string
required
The unique identifier for the product to delete. Must have the prefix ‘pr_’
Slug: TICKET_TAILOR_MCP_PRODUCTS_GETReturns 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.

Input Parameters

number
The maximum number of items to return.
string ("on_sale" | "hidden" | "sold_out")
The status of the product
number
Unix timestamp for created at date
number
Unix timestamp for updated at date
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for updated at date greater than
number
Unix timestamp for updated at date less than
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
number
Unix timestamp for updated at date greater than or equal to
number
Unix timestamp for updated at date less than or equal to
string
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_PRODUCT_UPDATEUpdates an existing product. 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.

Input Parameters

string
Name of the product
integer
Cost of the product in cents
string
Product status: on_sale, hidden or sold_out
string
Currency that the product can be purchased in. Defaults to the box office currency.
integer
Number of products available for purchase
string
required
The unique identifier for the product. Must have the prefix ‘pr_’
string
The ID of a voucher of type gift card to associate with the product. Must start with ‘vo_’ prefix. Mutually exclusive with issue_ticket_voucher and membership_type_id.
integer
Optional booking fee in cents which is charged per product to the customer and the funds are paid to you. We would recommend charging no more than 10% of the product price.
string
Description of the product
string
Instructions on how to purchase the product
string
Number of products to add or remove. The number should be preceded by a + or - sign
array
List of event series IDs that have the product with association values (‘1’ = add, ‘0’ = remove, ” = do nothing)
string
The ID of a membership type to associate with the product. Must start with ‘mt_’ prefix. Mutually exclusive with issue_ticket_voucher and voucher_id.
integer
Number of products available for purchase per event
string ("true" | "false")
If set to ‘true’, the quantity will be set to unlimited. Otherwise, it will be set to the quantity given
string
Indicate whether the QR code is to be issued for the product. Mutually exclusive with voucher_id and membership_type_id.
string
Indicate whether the product is linked to all event series
Slug: TICKET_TAILOR_MCP_STORE_GETRetrieves the current store configuration including store ID, currency, name, payment methods, and associated products. This provides comprehensive information about your Ticket Tailor store setup and configuration. Useful for understanding your store’s current settings and associated resources. This is a read-only operation that returns store 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.

Input Parameters

string
required
The ID (prefixed with ‘st_’) of the store to get
Slug: TICKET_TAILOR_MCP_STORE_LISTRetrieves a list of all stores associated with the provided API key. This tool is useful for managing multiple stores within your Ticket Tailor account. It returns a list of store IDs, names, and other relevant details for each store. This is a read-only operation that does not modify 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.
Slug: TICKET_TAILOR_MCP_STORE_UPDATEUpdates the store configuration including currency, name, and associated products. This allows you to modify your Ticket Tailor store settings such as changing the currency, updating the store name, or managing which products are available in the store. The currency can be set to various supported currencies, and products can be added or removed by providing an array of product IDs. Empty products array will remove all products from the store. 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.

Input Parameters

string
Name of the store
string
required
The ID (prefixed with ‘st_’) of the store to update
string ("gbp" | "usd" | "eur" | "sgd" | "aud" | "brl" | "cad" | "czk" | "dkk" | "hkd" | "huf" | "ils" | "jpy" | "myr" | "mxn" | "nok" | "nzd" | "php" | "pln" | "rub" | "sek" | "chf" | "twd" | "thb" | "try")
The currency code used by the store
array
Array of product IDs that are sold in the store. Empty array will remove all products from the store. Product IDs should be prefixed with ‘pr_’
Slug: TICKET_TAILOR_MCP_TICKET_GROUP_DELETEDelete a ticket group. This action is irreversible. The ticket group will be permanently removed and any associated ticket types and bundles will be removed from the group. 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.

Input Parameters

string
required
The unique identifier for the event series. Must have the prefix ‘es_’
string
required
The unique identifier for the ticket group to delete. Must have the prefix ‘tg_’
Slug: TICKET_TAILOR_MCP_TICKET_GROUP_UPDATEUpdates an existing ticket group. 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.

Input Parameters

string
Name of the ticket group
array
Array of bundle IDs that belong to this group. Bundle id must have the prefix ‘bu_’
integer
Maximum number of ticket types that this group can sell
integer
Maximum number of tickets of this group that can be purchased in a single order. Prevents bulk purchases and ensures fair distribution
integer
Minimum number of tickets of this group that must be purchased in a single order. Useful for group discounts or package deals
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
string
required
The unique identifier for the ticket group. Must have the prefix ‘tg_’
array
Array of ticket type IDs that belong to this group. Ticket type id must have the prefix ‘tt_’
Slug: TICKET_TAILOR_MCP_TICKET_TYPE_DELETEDelete a ticket type. This action is irreversible. The ticket type 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.

Input Parameters

string
required
The unique identifier for the ticket type to delete. Must have the prefix ‘tt_’
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
Slug: TICKET_TAILOR_MCP_TICKET_TYPE_UPDATEUpdates an existing ticket 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.

Input Parameters

string
Name of the ticket type
integer
Cost of the ticket type
string ("ON_SALE" | "SOLD_OUT" | "UNAVAILABLE" | "HIDDEN" | "ADMIN_ONLY" | "LOCKED")
Event series status
string
ID of the group this ticket type belongs to. Group id must have the prefix ‘tg_’
array
An array of associated discount ids with association values (‘1’ = add, ‘0’ = remove, ” = do nothing)
integer
Timestamp in seconds when the ticket type should be hidden until.
integer
Timestamp in seconds when the ticket type should be hidden after.
string
Code to access a hidden ticket
integer
Optional booking fee which is charged per ticket type to the customer and the funds are paid to you. We would recommend charging no more than 10% of the ticket price.
string
Description of the ticket type
string ("true" | "false")
Set the number of available tickets to zero
integer
Maximum number of tickets allowed per order
integer
Minimum number of tickets allowed per order
string
required
The unique identifier for the ticket type. Must have the prefix ‘tt_’
string
required
The unique identifier for the event series. Must have the prefix ‘es_’
string
Number of ticket types to add or remove. The number should be preceded by a + or - sign
boolean
Hide the ticket when it has sold out
string ("true" | "false")
Specifies whether to show the number of tickets still available
integer
Only show number of tickets still available when the available quantity is equal to or lower than this threshold
Slug: TICKET_TAILOR_MCP_VOUCHER_BY_ID_GETReturns a voucher 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.

Input Parameters

string
required
The unique identifier for the voucher. Must have the prefix ‘vo_’
Slug: TICKET_TAILOR_MCP_VOUCHER_CODES_GETReturns a list of voucher codes. 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.

Input Parameters

number
The maximum number of items to return.
number
Unix timestamp for expiry at date
number
Unix timestamp for created at date
string
required
The unique identifier for the voucher. Must have the prefix ‘vo_’
number
Unix timestamp for expiry at date greater than
number
Unix timestamp for expiry at date less than
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for expiry at date greater than or equal to
number
Unix timestamp for expiry at date less than or equal to
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_VOUCHER_CODE_VOIDVoids a voucher code. This action is irreversible. This will only mark one voucher code as voided, and will not impact the other related codes. 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.

Input Parameters

string
required
The unique identifier for the voucher. Must have the prefix ‘vo_’
string
required
The unique identifier for the voucher code. Must have the prefix ‘vc_’
Slug: TICKET_TAILOR_MCP_VOUCHER_CREATECreates a new voucher system with associated voucher codes. Vouchers are flexible promotional tools that can be used as either promotional codes (for marketing campaigns), or gift vouchers (for customer gifting), or as credit in lieu of a payment refund. Promotional vouchers have predefined codes, while gift vouchers and credit vouchers generate unique codes when issued. Vouchers can be restricted to specific event series and have configurable expiration dates and redemption rules. 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.

Input Parameters

string
required
A descriptive name for the voucher system (e.g., ‘Summer Sale Vouchers’, ‘Gift Cards’, ‘Loyalty Rewards’). This appears in your admin dashboard for easy identification
array
For PROMO type vouchers, provide an array of specific voucher codes (e.g., [‘SUMMER20’, ‘WELCOME10’]). These codes will be available for customers to use. Leave empty for gift vouchers and credit vouchers which generate unique codes automatically
integer
required
The monetary value of each voucher in cents (e.g., 1000 = $10.00). This is the amount that will be deducted from the order total when the voucher is redeemed
integer
required
Unix timestamp (in seconds) when all vouchers in this system expire. After this date, no vouchers can be redeemed. Set far in the future for long-term campaigns
string ("30" | "90" | "365")
For GIFT_CARD type vouchers, the number of days from issue date when the gift card expires. 30 = 1 month, 90 = 3 months, 365 = 1 year
string ("PROMO" | "GIFT_CARD")
The type of voucher system: ‘PROMO’ for marketing campaigns with predefined codes, ‘GIFT_CARD’ for gift vouchers or credit vouchers with unique generated codes. Defaults to ‘PROMO’ if not specified
array
Array of event series IDs where these vouchers can be used. If empty, vouchers can be used on any event series. Useful for targeted promotions. Event series id must have the prefix ‘es_’
boolean
When true, customers can use a voucher multiple times until its full value is consumed. When false, the voucher must be used in a single transaction and any unused balance will be lost
Slug: TICKET_TAILOR_MCP_VOUCHER_DELETEDelete voucher and its associated voucher codes. This action is irreversible. The voucher and its voucher codes 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.

Input Parameters

string
required
The unique identifier for the existing voucher to delete. Must have the prefix ‘vo_’
Slug: TICKET_TAILOR_MCP_VOUCHERS_GETReturns a list of vouchers. 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.

Input Parameters

number
The maximum number of items to return.
number
Unix timestamp for expiry at date
number
Unix timestamp for created at date
number
Unix timestamp for expiry at date greater than
number
Unix timestamp for expiry at date less than
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for expiry at date greater than or equal to
number
Unix timestamp for expiry at date less than or equal to
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
Slug: TICKET_TAILOR_MCP_VOUCHER_UPDATEUpdates an exist ing voucher’s name and properties. 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.

Input Parameters

string
A descriptive name given to the voucher
array
An array of associated voucher codes
integer
Voucher value in cents
integer
Voucher’s expiry date as Unix timestamp
string ("30" | "90" | "365")
Only available when voucher_type is gift_card. Voucher’s expiry date is calculated from this number of days on day of issue
string
required
The unique identifier for the existing voucher. Must have the prefix ‘vo_’
array
An array of associated event series IDs with association values (‘1’ = add, ‘0’ = remove, ” = do nothing)
Slug: TICKET_TAILOR_MCP_WAITLIST_SIGNUP_DELETEDelete event series waitlist signup. 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.

Input Parameters

string
required
The unique identifier for the event series that the waitlist signup is part of. Must have the prefix ‘es_’
string
required
The unique identifier for the waitlist signup to delete. Must have the prefix ‘ws_’
Slug: TICKET_TAILOR_MCP_WAITLIST_SIGNUPS_GETReturns a list of waitlist signups. 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.

Input Parameters

string
Used for filtering waitlist signups by email
number
The maximum number of items to return.
string
Used for filtering waitlist signups by events they belong to. Event id must have the prefix ‘ev_’
number
Unix timestamp for created at date
boolean
Used for filtering notified waitlist signups
number
Unix timestamp for created at date greater than
number
Unix timestamp for created at date less than
string
The ID of the first item in the next page.
number
Unix timestamp for created at date greater than or equal to
number
Unix timestamp for created at date less than or equal to
string
The ID of the last item in the previous page. Notes for LLMs: - Cursor-based (e.g. “or_1234”) pagination via the “starting_after” and “ending_before” parameters. - Both parameters take an existing value and return objects oldest to newest (lowest id to highest id). - If both parameters are provided, only “ending_before” is used. - “ending_before” (optional) - Returns objects listed before the named object. - “starting_after” (optional) - Returns objects listed after the named object - “ending_before” and “starting_after” must have prefixes. - “limit” (optional) - Limits the number of results per-page. Maximum: 100 - Example: to get the most recent (latest, newest) records, use “ending_before” parameter with a very large value (e.g. 2147483647) and then reverse the order of the results.
string
required
The unique identifier for the event series. Must have the prefix ‘es_’