swarmtix_checkout_questions_list
Lists the custom questions an event asks buyers during checkout
swarmtix_checkout_questions_list
Lists the custom questions an event asks buyers during checkout, one page at a time. Each entry carries the question's id, its wording, the field it maps to, and whether it is switched on and whether an answer is required.
When you would reach for it
- To check what buyers are being asked before an event goes live.
- To confirm a question landed after
swarmtix_checkout_questions_create. - To read the field names that the answers on an order line up against.
Scope
events:read
The questions are part of the event's setup. The answers are not here and are not covered by this scope — they arrive with each order under orders:read, on swarmtix_orders_list.
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
event | string | Yes | — | The event's id (a GUID) or its URL slug. |
limit | integer | No | 50 | How many questions to return. 1 to 200. |
cursor | string | No | — | The cursor from the end of a previous page. Omit to start at the beginning. |
Example call
{
"name": "swarmtix_checkout_questions_list",
"arguments": { "event": "spring-summit-2026" }
}What comes back
[
{
"id": "d0b62f47-5a19-4e83-91cd-7f3a2c6b58e0",
"eventId": "8f14e45f-ceea-467a-9c3d-1b2a5f6e7d80",
"question": "Any dietary requirements?",
"field": "Anydietaryrequirements",
"enabled": true,
"required": true
},
{
"id": "7a5e3c90-1b48-4f2d-86a7-0c9d5e1b4a26",
"eventId": "8f14e45f-ceea-467a-9c3d-1b2a5f6e7d80",
"question": "Which workshop track?",
"field": "Whichworkshoptrack",
"enabled": true,
"required": false
}
]| Field | What it is |
|---|---|
id | The question's id |
eventId | The event it belongs to |
question | The wording the buyer reads |
field | The internal field name, derived from the wording by stripping it down to letters and digits |
enabled | Whether the question is switched on at checkout |
required | Whether an answer is required to complete an order |
globalQuestionId | Present only when the question came from a shared question rather than being written for this event |
Questions come back in alphabetical order by wording, with the id as a tiebreak.
Only six fields are published, and that is deliberate rather than an oversight. The record also has an "has options" flag and an options list, but neither is populated on this read path — every row comes back with no options regardless of how the question is really configured. Publishing them would state that no question has a fixed list of answers, which would be wrong rather than merely missing.
What happens when you call it
- The event identifier is resolved and the ownership checks run. The service behind this tool applies no ownership check of its own, so this gate is the entire control — without it, the tool would answer for any event id a caller typed.
limitis checked.- The event's questions are fetched in one unbounded list.
- The list is sorted by wording, case-insensitively, then by id.
- One page is cut, projected to the fields above, and serialized.
Troubleshooting
"Event not found, or this connection does not have access to it."
The event does not exist, or it belongs to a different organisation than this connection covers.
A question you created is missing its answer options
Questions with a fixed list of answers to choose from are configured in the dashboard, and this tool does not report their option lists — see the note above. The question itself will be listed; its choices will not.
The list is empty
The event asks no custom questions. Buyers still give their name and email; those are standard checkout fields rather than custom questions.
"cursor is not valid: the question it points at is no longer in this list."
The question named by the cursor has gone between the two calls. Start the list again.
"This connection is not authorized for events:read. Reconnect and grant it to use this tool."
Reconnect and approve events:read.
Use cases
- Pre-event readiness — confirming the questions you need answers to are switched on
- Reconciling answers — matching the
fieldnames against the answers carried on each order - Review after a setup run — checking what an assistant added
- Auditing what you collect — the shortest list of the personal data your checkout asks for