- Brand
- Duesy
- Category
- Finance
- Primary Subcategory
- Event Organizer & Box-Office Tools
Integration details
Description
Duesy is an event ticketing and membership platform for organizers of tournaments, leagues, and live events. This plugin connects ChatGPT to your Duesy account so you can ask about your events in plain language. What you can do: - Find events across the organizations you manage, filtered by name, status (draft, live, complete), or date. - Get ticket, sales, and revenue totals for an event. - Review ticket types: prices, availability and usability windows, and limits. - Look up individual orders and issued tickets: who bought what and when, searchable by name, email, phone, or card last four, including check-in scans. - List and create short links for your organization, for example a short link to an event's ticketing page. - Find, add, update, and remove people such as coaches and attendees, including their team names; adding someone whose email or mobile is already on file returns the existing person instead of a duplicate. - Issue free coach passes to a coach for an event, or add more passes to their order later; Duesy texts and emails the coach a link to their passes, and a coach gets one coach-pass order per event. - Create, update and delete events, ticket types, ticket categories, venues and tournament categories; mark a ticket used or change until when it can be used; resend a purchaser their tickets link; get the link that opens an order's tickets. Who it is for: event organizers and staff with a Duesy account. You sign in with your Duesy credentials, and ChatGPT only sees data your Duesy role already lets you see. Limitations: the plugin cannot sell or refund tickets, issue payouts, or send messages of its own. The only messages it causes are the ones Duesy sends for an action: the coach-pass text and email, a resent tickets link, and the welcome text an event sends when a ticket is marked used. Every change needs the same Duesy permissions as the dashboard, a live event or one with sales cannot be deleted, and a person with sales, payments, messages, or teams cannot be removed. Money is reported in US dollars.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Event Organizer & Box-Office Tools
- Secondary Subcategories
- None listed
- Brand
- Duesy
- Access
- Account required
- First tracked
- 2026-11-21
- Tool count
- 46
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Duesy suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for Duesy
Get updates when Duesy’s Discoverability Score or category rank changes.
Competing in ChatGPT Event Organizer & Box-Office Tools
View Category46 tools agents can invoke
Use this when a coach who already has coach passes for an event needs more ("Jordan needs 2 more coach passes", "add another pass to Jordan's order"), or when `issue_coach_passes` refused because the coach already has a sale on the event. Adds free coach passes to that existing coach-pass sale and then texts and emails the person that more passes were assigned. Confirm with the user before calling it, since the result cannot be taken back. Pass `sale_id` (from `list_sales` filtered by `event_id` and `person_id`, from `get_sale`, or from the `issue_coach_passes` refusal); the sale must hold at least one coach pass that is not voided or refunded, and its person must have an email, or a mobile that can receive texts, on file. `quantity` (1 to 100) defaults to 1. The new passes use the sale's coach-pass ticket type. Repeating the same call within 10 minutes returns the sale without adding passes or messaging again, so to add passes twice on purpose, add them in one call. Acts only on organizations where the signed-in user holds the Events and Tickets permissions; it moves no money. Returns the sale in the same shape as `get_sale`; `list_tickets` with `sale_id` lists the passes. Do not use for a coach's first passes on an event, or when all their passes were voided or refunded; use `issue_coach_passes`. Returns `not_found` if the sale is inaccessible, or `invalid_argument` if validation fails.
add_coach_passes
Use this when the user wants an event's ticket types checked for setup mistakes before or during sales. Pass the event `id` from `list_events`. Checks day-name mismatches, coverage gaps, sibling price outliers, availability versus usability windows, promo overlap, discount-label dates, coach-pass setup and other oddities, and returns `findings` (severity, code, message, ticket type ids) plus a plain-text `report` written to be shown as it is. `halted` is true when a cluster of priced tickets shares an endpoint outside the event window, which suggests the event dates themselves are wrong; the other checks are then skipped until the user confirms the event start and end. If the user confirms the event dates are right and the shared endpoint is intentional (for example tickets kept usable after the event), call again with `bypass` listing that finding's `code`: the other checks run, the finding comes back with `bypassed: true` under Bypassed in `report`, and `halted` is false. `bypass` is for after the user has confirmed, not before. Changes nothing and sends nothing. Do not use for sales or revenue figures; use `get_event_statistics`. Returns `not_found` if the event does not exist or the caller cannot access its organization.
audit_event
Use this when the user wants a new tournament category (a sport or activity such as "Baseball", not a ticket category) added to an organization. Pass `organization_id` (from `list_organizations`) and `name`. It changes no existing categories, events or teams, does not attach the category to an event (do that with `category_id` on `create_event` / `update_event`), and does not set ages or classifications (those are managed in the Duesy dashboard). Acts only on organizations where the signed-in user holds the Categories permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the created category in the same shape as `get_category`. Do not use for a ticket category; use `create_ticket_category`. Returns `not_found` if the organization is inaccessible, or `invalid_argument` if validation fails.
create_category
Use this when the user wants a new event (tournament) added to one of their organizations. Creates the event as a `draft` unless `state` says otherwise; `live` publishes it and puts it on sale to the public, so confirm that with the user first. Pass `organization_id` (from `list_organizations`), `name`, `starts_at` and `ends_at`; the other fields are optional and mirror `get_event`, with `category_id` from `list_categories` and `location_ids` from `list_locations`. Duesy adds a free coach-pass ticket type to every new event; add the other ticket types with `create_ticket_type`. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the created event in the same shape as `get_event`. Do not use to change an existing event; use `update_event`. Returns `not_found` if the organization is inaccessible, or `invalid_argument` if validation fails.
create_event
Use this when the user wants a new venue added to an organization. Pass `organization_id` (from `list_organizations`), `name`, `tax_rate` (percent: 8.25 means 8.25%, 0 for none) and an `address` with `street_1`, `locality`, `region` and `postal_code` (`street_2` optional). The country is always US. It does not attach the venue to an event: do that with `update_event`'s `location_ids`. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the created location in the same shape as `get_location`. Do not use to change an existing venue; use `update_location`. Returns `not_found` if the organization is inaccessible, or `invalid_argument` if validation fails.
create_location
Use this when the user wants a contact such as a coach or an attendee added to an organization. Pass `organization_id` (from `list_organizations`), `first`, `last` and `person_types` (`coach` and/or `attendee`); `email`, `mobile` and `teams` are optional, and each team name links the organization's team of that name (ignoring case) or creates it. Before creating, it looks for a person in the organization with the same email or mobile: when there is one, it is returned unchanged with `matched: true` and nothing is written (change it with `update_person`); when the email and mobile belong to different people, it returns `conflict` naming their ids. Acts only on organizations where the signed-in user holds the People permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the person in the same shape as `get_person`, plus `matched`. Do not use to give a coach passes; use `issue_coach_passes` once the person exists. Returns `not_found` if the organization is inaccessible, or `invalid_argument` if validation fails.
create_person
Use this when the user wants a short link that forwards to a URL they supply, such as an event's public ticketing page. Pass `organization_id` (from `list_organizations`) and `destination_url`; `url_key` sets a custom slug and is otherwise generated. Repeating the same call within 10 minutes returns the link the first call created, so to make a second link to the same destination, pass a different `url_key`. Acts only on organizations where the signed-in user holds the Links permission. Anyone who opens the link is forwarded to that destination; Duesy stores the URL and does not visit it. Returns `{url, organization_id, destination_url, url_key, created_at}` with the public link in `url`. Do not use for the link that opens a sale's tickets; use `get_sale_link`. Returns `not_found` if the organization is inaccessible, or `invalid_argument` if validation fails, including a taken `url_key`.
create_short_url
Use this when the user wants a new ticket category (an organization-wide label for ticket types, such as "Spectator") added to an organization. Pass `organization_id` (from `list_organizations`) and `name`; `color` (hex, e.g. "#1d4ed8") is optional. It changes no existing categories or ticket types: assign the new category to a ticket type with `ticket_category_id` on `create_ticket_type` or `update_ticket_type`. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the created category in the same shape as `get_ticket_category`. Do not use for a tournament category; use `create_category`. Returns `not_found` if the organization is inaccessible, or `invalid_argument` if validation fails.
create_ticket_category
Use this when the user wants a new ticket type added to an event, such as a day pass or a weekend pass. Pass `event_id` (from `list_events`), `name` and the `usable_at` / `usable_until` window; the other fields are optional and mirror `get_ticket_type` (`price` is integer cents). `item_validation_limit` usually matches the usability window's day count: 1 for a single-day type, 3 for a three-day type. Setting `is_coach_pass: true` makes this the event's coach pass (price must be 0) and clears the flag from any other type. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the created ticket type in the same shape as `get_ticket_type`. Do not use to change an existing type; use `update_ticket_type`. Returns `not_found` if the event is inaccessible, or `invalid_argument` if validation fails.
create_ticket_type
Use this when the user wants a tournament category (not a ticket category) removed. Pass the category `id` from `list_categories` or `get_category`. There is no undelete, so confirm the exact category with the user first. A category an event or team still uses cannot be deleted and returns `invalid_argument` with the counts; an event's category can be changed with `update_event` until teams register, and a team's category cannot be changed, so a category with teams stays. Acts only on organizations where the signed-in user holds the Categories permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the deleted category in the same shape as `get_category`. Do not use for a ticket category; use `delete_ticket_category`. Returns `not_found` if the category is inaccessible or already deleted.
delete_category
Use this when the user wants a draft or completed event removed, along with its public ticketing page. Pass the event `id` from `list_events` or `get_event`. There is no undelete, so confirm the exact event with the user first. A `live` event cannot be deleted (move it to `draft` or `complete` with `update_event` first), and an event with any sale cannot be deleted at all; both return `invalid_argument` naming the rule. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the deleted event in the same shape as `get_event`. Returns `not_found` if the event is inaccessible or already deleted.
delete_event
Use this when the user wants a venue removed from an organization. Pass the location `id` from `list_locations` or `get_location`. There is no undelete, so confirm the exact venue with the user first. A venue an event still uses cannot be deleted and returns `invalid_argument` with the count: remove it from those events with `update_event`'s `location_ids` first. Past sales at the venue do not block the delete. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the deleted location in the same shape as `get_location`. Returns `not_found` if the location is inaccessible or already deleted.
delete_location
Use this when the user wants a contact with no history removed from an organization. Pass the person `id` from `list_people` or `get_person`. There is no undelete, so confirm the exact person with the user first. Only a person with no related records can be deleted: any sales, tickets, transactions, payment methods, subscriptions, point-of-sale orders, messages, notes, communications, SMS consents, verification codes, teams (as member or coach), seasons, metadata, addresses, registration entries, payments, form submissions, or linked payers or participants block it, and the `invalid_argument` error names each blocking relationship; unlink teams with `update_person` (`remove_teams`) first. Acts only on organizations where the signed-in user holds the People permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the deleted person in the same shape as `get_person`. Returns `not_found` if the person is inaccessible or already deleted.
delete_person
Use this when the user wants a ticket category removed. Pass the category `id` from `list_ticket_categories` or `get_ticket_category`. There is no undelete, so confirm the exact category with the user first. A category a ticket type still uses cannot be deleted and returns `invalid_argument` with the count: move event ticket types to another category (or clear it) with `update_ticket_type` first; organization-level pass types can only be changed in the Duesy dashboard. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the deleted category in the same shape as `get_ticket_category`. Do not use for a tournament category; use `delete_category`. Returns `not_found` if the category is inaccessible or already deleted.
delete_ticket_category
Use this when the user wants a ticket type removed from an event. Pass the type `id` from `list_ticket_types` or `get_ticket_type`. There is no undelete, so confirm the exact type with the user first. A type with tickets issued cannot be deleted and returns `invalid_argument`; draft (unfinished) tickets do not block it. The event's coach pass type may be deleted like any other. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the deleted ticket type in the same shape as `get_ticket_type`. Returns `not_found` if the type is inaccessible or already deleted, or `invalid_argument` if it is an organization-level pass, which this tool does not delete.
delete_ticket_type
Use this when the tournament category `id` is already known (from `list_categories`). Returns its `name` and `organization_id`; ages and classifications are managed in the Duesy dashboard and are not returned. Pass `include_counts: true` to add `events_count` and `teams_count`. Do not use for a ticket category; use `get_ticket_category`. Returns `not_found` if the category does not exist, was deleted, or the caller cannot access its organization.
get_category
Use this when the event `id` is already known (from `list_events`) and the user needs its full record: dates, state, descriptions, settings (`item_validation_limit`, `post_validation_message`, `hide_from_org_listing`), `default_coaches_passes`, `team_count`, public ticketing `url`, tournament `category`, attached `locations` (each with `address` and `tax_rate`) and the embedded `organization` (`id`, `name`, `short_name`, `timezone`). Returns catalog data only. Do not use for sales, ticket or revenue figures; use `get_event_statistics`. Returns `not_found` if the event does not exist or the caller cannot access its organization.
get_event
Use this when the user asks how an event sold: ticket counts, sales counts, revenue, refunds, fees, coach passes sent, or breakdowns by ticket type, venue, purchase channel or timing. Pass the event `id` from `list_events`. `totals` carries `sales`, `tickets_sold`, `coaches_sent` and the money figures (`gross_revenue`, `net_revenue`, `platform_fees`, `merchant_fees`, `refunds_total`) as `{amount, currency}` in cents. `timing` splits tickets into `pre` / `intra` / `post` the event window. `sources` splits tickets and sales into `agent_assisted` and `self_served`, which sum to `total`; `tap_to_pay` is a subset of `agent_assisted` and `apple_pay` a subset of `self_served`. `wallet_passes`, `new_vs_returning`, `ticket_types` (each with its `ticket_category`) and `locations` give the other breakdowns. `sales` and `tickets_sold` exclude refunded items and coach passes, so they differ from the raw `include_counts` figures on `list_events`. `totals` and the rollups come from separately cached tiers and can differ slightly while an event is actively selling; report `totals` as the headline. An event with no sales returns zeros. `{"status": "pending"}` means the figures are not ready yet, not zero sales. One call returns everything; the figures do not need polling. Do not use to look up individual orders or tickets; use `list_sales` or `list_tickets`. Do not use for an event's dates, settings or venues; use `get_event`. Returns `not_found` if the event does not exist or the caller cannot access its organization.
get_event_statistics
Use this when the location `id` is already known (from `list_locations`, an event's `locations` or a sale's `location`). Returns its `name`, `tax_rate` in percent, embedded street `address` and `organization_id`. Pass `include_counts: true` to add `events_count`. Returns `not_found` if the location does not exist, was deleted, or the caller cannot access its organization.
get_location
Use this when more detail about one organization is needed than the `id`, `name`, `short_name` and `timezone` embedded in event and sale responses: it adds `contact` and `telephone`. Pass the organization `id` from `list_organizations`. Returns `not_found` if the organization does not exist or the caller cannot access it.
get_organization
Use this when the person `id` is already known (from `list_people`, `create_person` or a sale's `person.id`). Returns the person in the same shape as `list_people`: `first`, `last`, `email`, `mobile` (E.164), `organization_id`, `person_types` and linked `teams`. Returns `not_found` if the person does not exist, was deleted, or the caller cannot access their organization.
get_person
Use this when the sale `id` is already known (from `list_sales`, a ticket's `sale.id` or `issue_coach_passes`) and the order's detail is needed. Returns the sale in the same shape as `list_sales`: money figures in cents, `published_at`, `notes`, `is_new_attendee`, and embedded `organization`, `event`, `location`, purchaser `person`, `teams` and `payment_method`. The tickets it issued are listed by `list_tickets` with `sale_id`. Returns `not_found` if the sale does not exist, is not published, or the caller cannot access its organization.
get_sale
Use this when someone needs the link that opens a sale and its tickets or passes ("get me the link to Jordan's coach passes"), the same link the Duesy dashboard copies for a sale. Pass `sale_id` (from `list_sales`, `get_sale`, `issue_coach_passes` or a ticket's `sale.id`); the sale must be published. Returns `{url, organization_id}`; the sale's link is created the first time it is asked for and the same link is returned after that. Anyone holding the link can open the sale's tickets, so share it only with the purchaser. Sends nothing, contacts no outside system and moves no money. Acts only on organizations where the signed-in user holds the Events and Tickets permissions. Do not use to make a short link to a URL; use `create_short_url`. Do not use to send the purchaser their tickets; use `resend_sale`. Returns `not_found` if the sale is inaccessible or not published.
get_sale_link
Use this when the ticket `id` is already known (from `list_tickets`) and one ticket's detail or scan history is needed. Returns the ticket in the same shape as `list_tickets`, with the embedded `sale` (`{id}`, pass it to `get_sale` for the order), `ticket_type` and holder `person`. Pass `include_validations: true` to add its `validations` (scans and lookups, oldest first). Returns `not_found` if the ticket does not exist, its sale is not published, or the caller cannot access its organization.
get_ticket
Use this when the ticket category `id` is already known (from `list_ticket_categories` or a ticket type's `ticket_category`). Returns its `name`, hex `color` (or null) and `organization_id`. Pass `include_counts: true` to add `ticket_types_count`. Do not use for a tournament category; use `get_category`. Returns `not_found` if the category does not exist, was deleted, or the caller cannot access its organization.
get_ticket_category
Use this when the ticket type `id` is already known (from `list_ticket_types`) and the full record is needed: price, availability and usability windows, validation limit, `hidden`, `is_agent_only`, `is_coach_pass` and the embedded `ticket_category`. Pass `include_counts: true` to add `sales_count`. Returns `not_found` if the type does not exist or the caller cannot access its organization.
get_ticket_type
Use this when the user wants to give a coach their first coach passes for an event ("give Jordan Reyes 3 coach passes for the Spring Classic", "send the Thunder coach their passes"). Creates a free coach-pass sale for the person on the event, with no payment, tags the person a coach, and then texts and emails the person a link to their passes. Confirm with the user before calling it, since the result cannot be taken back. Pass `event_id` (from `list_events`), `person_id` (from `list_people` or `create_person`; the person must belong to the event's organization and have an email, or a mobile that can receive texts, on file) and `ticket_type_id`, the event's coach-pass ticket type (`is_coach_pass: true` on `list_ticket_types`; no other type can be issued this way). `quantity` (1 to 100) defaults to the event's default coach pass count. `teams` names the teams the passes are for; each links the organization's team of that name to the person and the sale, or creates it. A person gets one coach-pass sale per event: when they already hold one that is not voided or refunded, it returns `invalid_argument` naming that sale's id and creates nothing. Repeating the same call within 10 minutes returns the first sale and does not message the person again. Acts only on organizations where the signed-in user holds the Events and Tickets permissions; it moves no money. Returns the sale in the same shape as `get_sale`. Do not use to give a coach who already has passes on the event more of them; use `add_coach_passes`. Returns `not_found` if the event or person is inaccessible, or `invalid_argument` if validation fails.
issue_coach_passes
Use this when the user asks about tournament categories, the sport or activity an organization's events and teams are grouped under (for example "Baseball" or "Fastpitch"), or needs a category's `id` for `category_id` on `create_event` / `update_event`. Returns the categories in the organizations the signed-in user can access, sorted by name, each with `name` and `organization_id`; ages and classifications are managed in the Duesy dashboard and are not returned. Filter by `organization_id` (from `list_organizations`). Pass `include_counts: true` to add `events_count` and `teams_count`. Do not use for ticket categories, the labels on ticket types; use `list_ticket_categories`.
list_categories
Use this when the user wants to find events (tournaments), browse upcoming or past events, or needs an event's `id` for another tool. Returns a paginated list of the events the signed-in user can access, most recent start date first. Each event carries its dates, `state` (`draft`, `live` or `complete`), settings, public ticketing `url`, `team_count`, `default_coaches_passes`, tournament `category` and attached venues as `locations`, in the same shape as `get_event`. Filter with `name` (case-insensitive substring), `organization_id` (from `list_organizations`), `state`, or a `starts_at_after` / `starts_at_before` window (both exclusive). Pass `include_counts: true` to add `sales_count` and `tickets_count` per event; omit it when the counts are not needed, since it runs extra queries. Do not use for sales, ticket or revenue totals; use `get_event_statistics`.
list_events
Use this when the user asks about an organization's venues, or needs a location `id` for `update_event`'s `location_ids` or the `location_id` filter on `list_sales` / `list_tickets`. A location is a venue an organization sells tickets at, with a street `address` and a sales `tax_rate` in percent (8.25 means 8.25%). Returns the locations in the organizations the signed-in user can access, sorted by name. Filter by `organization_id` (from `list_organizations`). Pass `include_counts: true` to add `events_count`.
list_locations
Use this when the user's organization is not yet known, or they ask which organizations they can see: most other tools take an `organization_id` from here. Returns a paginated list of the organizations the signed-in user can access, sorted by name, each with `id`, `name`, `short_name` and `timezone`. The `name` filter is a case-insensitive substring match on the name or short name.
list_organizations
Use this when the user wants to find a contact (a coach, attendee, participant or payer) in an organization, or needs a person `id` for `get_person`, `update_person`, `delete_person` or `issue_coach_passes`. Returns a paginated list of the people in the organizations the signed-in user can access, newest first, each with `first`, `last`, `email`, `mobile` (E.164), `organization_id`, `person_types` and linked `teams`. Filter by `organization_id`, `person_types` (people with any of the listed types) or a free-text `query` over name, email and mobile. When the user is about to add someone, `create_person` already returns an existing match by email or mobile instead of a duplicate.
list_people
Use this when the user asks who bought what and when: recent orders for an event, a purchaser's orders, or the sale `id` a coach's passes live on. A sale is one order, which may issue several tickets. Returns a paginated list of the published sales the signed-in user can access, most recent first, each with money figures (`base`, `tax`, `platform_fee`, `processing_fee`, as `{amount, currency}` in cents), `published_at`, `notes`, `is_new_attendee`, and embedded `organization`, `event` (null for an event-less pass), `location`, purchaser `person`, `teams` and `payment_method` (`{last_four}` or null). Drafts are excluded; refunded sales are listed at their original amounts. Filter by `organization_id`, `event_id`, purchaser `person_id`, `location_id`, `ticket_type_id` / `ticket_category_id` (sales that issued such a ticket), a `published_at_after` / `published_at_before` window (both exclusive), or a free-text `query` over the purchaser's name, email, mobile and card last four. The tickets a sale issued are not nested; use `list_tickets` with `sale_id`. Do not use for an event's totals or revenue; use `get_event_statistics`.
list_sales
Use this when the user asks which short links an organization has, or needs an existing link's destination or slug. Returns a paginated list of the organization's active short URLs, most recent first, each with the public `short_url`, `destination_url`, `url_key` slug and timestamps; deactivated links are excluded, and the links `get_sale_link` returns for sales are not listed. Pass `organization_id` (from `list_organizations`). Returns `not_found` if the organization does not exist or the caller cannot access it.
list_short_urls
Use this when the user asks about ticket categories, the organization-wide labels that group ticket types across events (for example "Spectator" or "Athlete"), or needs a category's `id` for a ticket type's `ticket_category_id`. Returns the ticket categories in the organizations the signed-in user can access, sorted by name, each with `name` and optional hex `color`. Filter by `organization_id` (from `list_organizations`). Pass `include_counts: true` to add `ticket_types_count`. Do not use for tournament categories, the sports or activities events are grouped under; use `list_categories`.
list_ticket_categories
Use this when the user asks what tickets an event sells, their prices, availability or usability windows, or needs a ticket type `id`, including the event's coach-pass type (`is_coach_pass: true`) for `issue_coach_passes`. Pass `event_id` (required, from `list_events`). Returns the event's ticket types in display order, each with `price`, availability window (when it can be bought), usability window (when the ticket can be used), `item_validation_limit`, `hidden`, `is_agent_only` (only signed-in agents can see and sell it; the public storefront withholds it like a hidden type), `is_coach_pass` and `ticket_category`. Pass `include_counts: true` to add `sales_count` (tickets of that type sold); omit it when only the catalog is needed. Do not use for revenue or per-type sales totals; use `get_event_statistics`.
list_ticket_types
Use this when the user asks about individual issued tickets: a holder's tickets, the passes on a sale, a ticket's scan history, or the ticket `id` for `mark_ticket_used` or `set_ticket_usable_until`. A ticket is one admission issued to one holder by a sale; a sale of three passes issues three tickets. Returns a paginated list of the tickets on published sales the signed-in user can access, newest first, each with `base` in cents, `voided_at`, `usable_at`, `usable_until` (the ticket's own usability end, null when it follows its ticket type), `is_new_attendee`, and embedded `organization`, `sale` (`{id}`), `ticket_type` and holder `person` (the assignee, else the purchaser). Voided tickets and coach passes are included. Filter by `organization_id`, `event_id`, `sale_id`, `ticket_type_id`, `ticket_category_id`, holder `person_id`, the sale's `location_id`, a `published_at_after` / `published_at_before` window on the sale (both exclusive), or a free-text `query` over the holder's and purchaser's name, email, mobile and the card's last four. Pass `include_validations: true` to add each ticket's `validations` (scans and lookups, oldest first). Do not use for an event's ticket counts; use `get_event_statistics`.
list_tickets
Use this when staff need a ticket recorded as used without scanning its QR code: someone was let in without a scan, or a holder asks staff to redeem their ticket ("mark Jordan's Saturday pass as used", "check in ticket 9f3c…"). Records one admission on the ticket, with the same checks as a gate scan: a voided or refunded ticket, one outside its usable window, or one at its use, per-period or per-event limit is refused with `conflict` naming each reason, and the refused attempt is kept in the ticket's scan history. Pass `ticket_id` (from `list_tickets` or `get_ticket`). `event_id` (from `list_events`) is only needed for an organization-wide pass that is capped per event. The use is recorded under the signed-in user with source "AI" in the ticket's scan history, counts toward the ticket's use limit, and cannot be given back by calling again. Confirm with the user before calling it, since the result cannot be taken back. Like a gate scan it can schedule the event's post-use welcome text to the holder, refresh a pass in Apple Wallet, and rotate the ticket's QR code when the organization rotates codes on scan; it moves no money. Repeating the same call within 10 minutes returns the first use without recording another. Acts only on organizations where the signed-in user holds the Ticketing permission, which every staff role down to Ticket Agent has. Returns `validation` (`{id, validated_at, status, status_label, event, location, agent, created_at}`) and `ticket` in the same shape as `get_ticket` with `include_validations: true`. Do not use to change when a ticket can be used; use `set_ticket_usable_until`. Returns `not_found` if the ticket is inaccessible or not published, or `invalid_argument` if validation fails.
mark_ticket_used
Use this when a purchaser or coach cannot find their tickets or passes and needs the link sent again ("resend Jordan's tickets", "Jane never got her passes"). Texts and emails the sale's purchaser the link to their tickets: a text to their mobile unless it opted out, and an email to their address. Confirm with the user before calling it, since the result cannot be taken back. Pass `sale_id` (from `list_sales`, searching by the purchaser's name, email or mobile, or filtering by `event_id` and `person_id`). The sale must be published and its purchaser must have an email, or a mobile that can receive texts, on file; add one with `update_person` first. The link goes to the purchaser, not to holders the tickets were assigned to. Changes no tickets and moves no money. Repeating the same call within 10 minutes sends nothing and returns `replayed: true`. Acts only on organizations where the signed-in user holds the Tickets permission. Returns `sale` in the same shape as `get_sale`, plus `emailed_to` and `texted_to` (the address or number used, or null) and `replayed`. Do not use to give a coach new passes; use `issue_coach_passes` or `add_coach_passes`. Returns `not_found` if the sale is inaccessible or not published, or `invalid_argument` if validation fails.
resend_sale
Use this when a ticket, or every ticket on a sale, should be usable until a different time than its ticket type allows: a ticket stopped scanning because its window ended, or a holder needs in later ("let Jordan's order be used through Sunday", "extend that day pass until 9 PM"). Sets each ticket's own `usable_until`, which the gate checks instead of the ticket type's. Pass exactly one of `sale_id` (every ticket the sale issued, voided ones included) or `ticket_id` (one ticket), and `usable_until`, a future datetime; pass `usable_until: null` to remove the override so the tickets follow their ticket type again. Only the end moves; when a ticket can first be used does not change. A time earlier than the ticket type's own `usable_until` shortens the window, so compare first. Sends no text or email and moves no money; a ticket its holder added to Apple Wallet gets a silent pass refresh from Apple. Acts only on organizations where the signed-in user holds the Events and Tickets permissions. Returns `tickets`, every changed ticket in the same shape as `get_ticket`. Do not use to record a ticket as used; use `mark_ticket_used`. Returns `not_found` if the sale or ticket is inaccessible or not published, or `invalid_argument` if validation fails.
set_ticket_usable_until
Use this when the user wants to rename a tournament category (not a ticket category). Pass the category `id` (from `list_categories` or `get_category`) and the new `name`, the only field this tool changes; the new name shows on every event and team using the category. Ages, classifications and which events use the category are changed in the Duesy dashboard. Acts only on organizations where the signed-in user holds the Categories permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the updated category in the same shape as `get_category`. Do not use for a ticket category; use `update_ticket_category`. Returns `not_found` if the category is inaccessible, or `invalid_argument` if validation fails.
update_category
Use this when the user wants to change an existing event: its name, dates, state, descriptions, settings, tournament category or venues. Pass the event `id` (from `list_events` or `get_event`) and only the fields to change; omitted fields keep their values and the full record is re-validated. Fields mirror `create_event`. Setting `state` to `live` publishes the event and puts it on sale to the public, and `draft` takes it off sale, so confirm a state change with the user first. `location_ids` replaces the whole set of venues: send every one to keep, or `[]` to remove all. `category_id` cannot change once teams have registered, and changing it clears the ages and classifications offered under the old category. Moving `starts_at` / `ends_at` also moves the usability window of the event's coach pass. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the updated event in the same shape as `get_event`. Returns `not_found` if the event is inaccessible, or `invalid_argument` if validation fails.
update_event
Use this when the user wants to change a venue's name, address or sales tax rate. Pass the location `id` (from `list_locations` or `get_location`) and only the fields to change (`name`, `tax_rate`, `address`); inside `address` only the parts sent change, and an explicit null `street_2` clears it. The country cannot change. The change applies to every event using the venue. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the updated location in the same shape as `get_location`. Returns `not_found` if the location is inaccessible, or `invalid_argument` if validation fails.
update_location
Use this when the user wants to change a contact's name, email, mobile, coach or attendee type, or team links. Pass the person `id` (from `list_people`, `get_person` or `create_person`) and only the fields to change: `first`, `last`, `email` and `mobile` overwrite the stored value, and a null `email` or `mobile` clears it (a payer must keep both). `add_person_types` / `remove_person_types` add or remove `coach` and `attendee`; participant and payer are always kept, and a person must keep at least one type. `add_teams` links each named team, creating it when there is none; `remove_teams` unlinks them and leaves the teams in place. Acts only on organizations where the signed-in user holds the People permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the updated person in the same shape as `get_person`. Returns `not_found` if the person is inaccessible or deleted, or `invalid_argument` if validation fails.
update_person
Use this when the user wants to rename or recolor a ticket category. Pass the category `id` (from `list_ticket_categories` or `get_ticket_category`) and only the fields to change (`name`, `color`); an explicit null `color` clears it. The change shows on every ticket type using the category, across all of the organization's events. To move a ticket type to a different category, use `update_ticket_type` with `ticket_category_id` instead. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the updated category in the same shape as `get_ticket_category`. Do not use for a tournament category; use `update_category`. Returns `not_found` if the category is inaccessible, or `invalid_argument` if validation fails.
update_ticket_category
Use this when the user wants to change an existing event ticket type: its name, price, windows, limits, visibility, category or coach-pass flag. Pass the type `id` (from `list_ticket_types` or `get_ticket_type`) and only the fields to change; omitted fields keep their values and the full record is re-validated. Fields mirror `create_ticket_type`. Setting `is_coach_pass: true` makes this the event's coach pass (price must be 0) and clears the flag from any other type. Acts only on organizations where the signed-in user holds the Events permission. Writes only to Duesy, contacts no outside system, sends no messages and moves no money. Returns the updated ticket type in the same shape as `get_ticket_type`. Returns `not_found` if the type is inaccessible, or `invalid_argument` if validation fails or the type is an organization-level pass, which this tool does not edit.
update_ticket_type
Duesy ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Duesy's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Duesy alternatives on ChatGPT?
As of 2026-11-21, Duesy competes with A Seat Awaits, ADG Events, AEvent, Alpha Events, Artist Growth, Booking OS, CatMai, Checkin and 36 more in ChatGPT Event Organizer & Box-Office Tools, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.