Tickets
Inbound requests to run a Blueprint. A ticket is the "this is what I want done" record — it captures who requested the work, which blueprint to run, and the input values. Tickets are typically created automatically by upstream events (form submissions, API callers, scheduled triggers); these endpoints are the read surface for inspecting them.
Scopes
| Scope | Reach |
|---|---|
blueprints:read | Listing, reading, viewing filters. |
TIP
Tickets are read-only via the public API. They are produced by the runtime when external triggers (forms, scheduled jobs, programmatic submissions) request a blueprint run. To inspect what happened after a ticket was processed, follow it to its Assembly.
Endpoints
List Tickets
GET /api/factory/tickets/
Returns a page of ticket records.
Required scope: blueprints:read · also accepts API key
Query parameters — standard pagination set; see Conventions › Pagination. Defaults: sort_by=created, sort_order=desc. (No hydrate flag on this resource.)
Response 200 — TicketInDbCursorPage
Get Ticket Filter Metadata
GET /api/factory/tickets/filters
Returns filter/operator/sort options for List Tickets.
Required scope: blueprints:read
Response 200 — open metadata object.
Get Ticket by ID
GET /api/factory/tickets/{id}
Returns a single ticket record.
Required scope: blueprints:read · also accepts API key
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string | yes | Ticket ID. |
Response 200 — TicketRead
See also
- Blueprints — the workflow definition a ticket targets.
- Assemblies — the execution record that follows a ticket.
- Forms › Submissions — form submissions are a common trigger for creating tickets.